Get Token Holders
Retrieve the top holders of any ERC-20 token via Sim Dune API, ranked by balance (largest first). Returns wallet addresses, token balances, percentage of supply, and USD values. Pagination: max 500/request, use nextOffset for additional holders. Ideal for: whale tracking, token distribution analysis, concentration risk detection, governance analysis, airdrop targeting.
Catalog action Blockchain Data
Retrieve the top holders of any ERC-20 token via Sim Dune API, ranked by balance (largest first). Returns wallet addresses, token balances, percentage of supply, and USD values. Pagination: max 500/request, use nextOffset for additional holders. Ideal for: whale tracking, token distribution analysis, concentration risk detection, governance analysis, airdrop targeting.
At a Glance
| Field | Value |
|---|---|
| Action ID | sim-dune-get-token-holders |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | sim-dune, blockchain, token, holders, distribution, whale, analytics, top-holders, concentration, governance, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
chainId | number | Yes | Chain ID where the token exists |
tokenAddress | string | Yes | Token contract address |
limit | number | No | Maximum number of holders to return (default: 500, max: 500) |
offset | string | No | Cursor for pagination (use nextOffset from previous response) |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
chainId | number | Yes | Chain ID queried |
tokenAddress | string | Yes | Token address queried |
holders | array | Yes | Token holders ranked by balance |
nextOffset | string | No | Cursor for next page of results |
Examples
json{ "type": "sim-dune-get-token-holders", "payload": { "chainId": 8453, "tokenAddress": "0x0000000000000000000000000000000000000000" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/sim-dune-get-token-holders/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "chainId": 8453, "tokenAddress": "0x0000000000000000000000000000000000000000" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.