Use your separate demo account, not your API provider login. Sign-in is saved only for this browser session.
Ethereum & BNB Smart Chain · Historical wallet transfers
Historical UTC windows up to 31 days. One asset per trace; no automatic swaps or bridge traversal. Up to 500 edges. Cloud: 20 API calls / 24 seconds, including pagination; local: 40 / 85 seconds. Scan up to 5 pages of 100 rows per address / direction. Limits are disclosed.
Enter an address to explore transfers, or load a sample to try the graph.
1. Enter starting addresses, choose a chain, direction, asset and UTC range, then run a trace. BSC and Binance-Peg USDT are selected by default. Load live example fills a verified historical BSC wallet and date range, then queries the real API.
2. Leave the destination blank to explore. Set a destination to find directed paths. Chronological paths exclude transfers ordered before the previous hop, but do not attribute funds.
3. Select edges for transaction details. Select addresses to add a local alias, start a new trace or expand one hop. Zooming and dragging do not make API calls.
4. Sample data covers only Wallet A–G on 2026-09-06, native assets and USDT. Other addresses return no sample matches. Live errors never fall back to sample data.
5. CSV exports filtered rows, JSON the entire result, and SVG the graph. A bounded graph is not the complete transfer network.
6. Live uses Kayalabs by default; Kaya is available in Advanced options. Both query historical wallet transfers. Pagination is scanned before direction and row limits are applied. If a scan limit is reached, narrow the date range; if a row limit is reached, increase rows per address. Native BNB and USDT are different assets; approvals, failed transactions and gas fees are not transfers.