Holders
Holder count and the largest token accounts, each with their share of supply.
Path parameters
| Field | Type | Description |
|---|---|---|
mintrequired | string | Token mint address (base58). |
Query parameters
| Field | Type | Description |
|---|---|---|
networkoptional | mainnet | devnet | Network to read. Devnet returns an empty payload (with a note) until its ingestor lands. default mainnet |
Response fields
| Field | Type | Description |
|---|---|---|
count | number | null | Holding accounts. When countIsFloor is true this is a LOWER BOUND, not an exact figure. |
countIsFloor | boolean | true = the bounded crawl hit its cap, so the real holder count is >= count (mega-caps like wSOL). false = exact. |
top[].address | string | The largest token ACCOUNT (not the owner wallet). |
top[].owner | string | null | The wallet that owns the token account (null while a pre-existing cache entry awaits its refresh). |
top[].uiAmount | number | Tokens held. |
top[].pct | number | null | % of total supply. |
top[].isPoolVault | boolean | true = a known AMM pool vault (dominant-pool vault or Raydium AMM v4 authority owner) — liquidity, not a whale. |
updatedAt | string | null | When holders were last refreshed (ISO). |
count comes from a bounded crawl (20k accounts). For widely-held tokens the crawl caps out and countIsFloor is true: the real count is >= count. Never read a countIsFloor:true count as exact.
top[].address is the token ACCOUNT; top[].owner is the wallet that owns it (the #1 account is typically an AMM pool vault, flagged with isPoolVault:true). Vault labels cover what we positively identified — the dominant pool's vaults and Raydium AMM v4 vaults; CLMM / other-venue vaults may go unflagged.