List ERC-20 transfers for an address
You want every token movement in or out of an address, not just a balance snapshot. The transfers endpoint returns a paginated, decoded list ordered by block. Full history comes from our archive nodes, so deep lookbacks work without extra setup.
- An API key (sk_live_...) with C1 read access.
- An address on eth or tron.
1Request the first page
GET the transfers path with limit and offset. The endpoint echoes both back so pagination is deterministic across requests.
curl "https://api.1st-node.com/v1/data/eth/address/0x53d2...9a1f/transfers?limit=100&offset=0" \ -H "Authorization: Bearer sk_live_..."
2Read decoded transfer items
Each item includes token symbol, decimals, counterparties, amount and block. No log parsing required — the transfers are already decoded from event logs.
> {
> "limit": 100,
> "offset": 0,
> "items": [
> { "block": 19875421, "token": "USDC", "from": "0x1f3c...", "to": "0x53d2...9a1f", "amount": "5000000" }
> ]
> }3Advance through pages
Increase offset by limit until items comes back shorter than limit. Because the endpoint echoes limit and offset, you can resume from any point without drift.
curl "https://api.1st-node.com/v1/data/eth/address/0x53d2...9a1f/transfers?limit=100&offset=100" \ -H "Authorization: Bearer sk_live_..."
常见问题
How deep can transfer history go?
Back to genesis. History is served from our own archive nodes, so archive-depth lookbacks (C2 for old ranges) work without you running an archive node.
Is the ordering stable between pages?
Yes. Items are ordered by block and the endpoint echoes limit and offset, so paging with a fixed limit is deterministic.
继续阅读
充值、拿密钥、上线。
自助开通。支持加密货币或银行卡。按额度计费——重型原语更贵，简单调用很便宜。
获取 API 密钥