Tools

Holder Snapshot

A CSV of every wallet holding a token, or every owner of an NFT collection, as of the moment you run it.

Open Holder Snapshot ↗Solana Token Holder Snapshot overview

Step by step

1. Step 1Pick Token or NFT
2. Step 2Enter the addressA token mint, with optional Top holders and minimum balance, or a collection address (a first verified creator also works). On Mainnet, popular tokens and collections are one click.
3. Step 3Read the holdersBalances are added up per owner wallet, and pools and other program-owned addresses are named and marked. The counts and the first 200 rows show on the page.
4. Step 4Sign one transactionExport CSV pays the snapshot fee: a SOL transfer with a memo naming the snapshot, on a review card before your wallet opens. Once per snapshot.
5. Step 5Download CSVToken: rank, owner, type, label, amount, raw amount, share of supply, token accounts and linked group. NFT: rank, owner, type, label and NFTs held.

When to use it

A snapshot records who holds a token at a given moment. Use it to plan an airdrop, reward holders, measure how concentrated a token is, or keep a record before a migration. Taking one is read-only and needs no wallet; a wallet is needed only to pay for the full CSV.

Token snapshots

• Paste the mint and take the snapshot: the name, logo and supply show before the scan, with a Token-2022 tag if it is one. On Mainnet, popular tokens are one click.
• Top holders keeps only the largest wallets; all, or blank on any token but a popular one, keeps every holder. On a popular token, up to 10,000 come from Birdeye's ranking in seconds, and a larger number reads every holder on-chain, 3–4 minutes for a million. The minimum balance filter drops dust holders; it's in whole tokens.
• Rows are ranked by balance, largest first, one row per owner wallet.

How holders are counted

• By owner wallet, not by token account. A wallet can hold the same mint in several token accounts; they're added up, so 60 in one and 40 in another is one wallet holding 100, and the CSV's token_accounts column says how many were merged.
• Token accounts with a zero balance are never counted, whichever RPC the scan runs on.
• Each address gets a type. wallet: on the ed25519 curve, so a keypair a person or a bot holds. program: an address a program controls, such as a pool, a bonding curve, a lock, a vault, a multisig or a marketplace escrow, named where the program is known, for example Raydium AMM v4 pool, Pump.fun bonding curve, Orca Whirlpool pool, Meteora DLMM pool, Jupiter limit order or SPL Token multisig. burn: the incinerator or the system program's address.
• Program-owned and burn addresses stay in the list and the CSV, marked, but aren't counted as wallets. The headline reads like "1,033 wallets · 27 program-owned · 1,069 token accounts".
• A popular token's top holders, up to 10,000, come from Birdeye's ranking, which already merges each wallet's accounts. Its total holder count is Birdeye's own figure, not a Solstack scan, and the counts on the page cover only the top holders you asked for. Ask for more than 10,000 and it's a full on-chain scan like any other token's, counted the same way.

A wallet isn't the same as a person: one person or bot can control many wallets. On a token snapshot, Find linked wallets checks the largest 100 wallets and merges those whose first SOL came from the same wallet, or whose first buy one wallet paid for, into linked groups. The result reads as about N independent holders among the wallets checked, and each linked wallet gets a group letter in the list and in the CSV's linked_group column. Exchanges and trading services that fund thousands of unrelated wallets don't count as links.

NFT collection snapshots

Enter the collection address; it's read 1,000 NFTs at a time, so any size works. A collection's first verified creator address, usually the candy machine creator shown on an NFT's page in most explorers, also works: each item's holder is then read one by one, for collections of up to 2,000 items. Either way the CSV has one row per owner with how many NFTs they hold, and marketplace escrows, vaults and staking programs are marked as program-owned rather than counted as wallets.

Sending to a snapshot

Paste the token CSV into Multisender with the amounts you want, or let Airdrop take the snapshot and send in one flow.

Past snapshots

A snapshot is saved under Past snapshots once its CSV is paid for, and from there it opens again or exports again at no charge; Re-run takes a new snapshot of current data. The last 30 per network are kept in this browser. Sign in to save to wallet, a message signature rather than a transaction, saves them to Solstack's backend instead, so they follow your wallet to other devices; the session lasts seven days. Snapshots saved before the fee existed stay and export free. You can remove one or clear them all at any time. A snapshot of more than 10,000 rows keeps its rows in the browser's larger IndexedDB store, and one of more than 150,000 rows stays in this browser even when you're signed in. If the browser runs out of storage, the oldest are dropped first and a very large one may keep only its summary, marked Summary only.

Limits

Every token scans in full, many ranges of addresses at once: most in seconds, a million holders in 3–4 minutes. Keep the tab open, and use a computer rather than a phone for the largest tokens. A token with more than 1.5 million token accounts is more than a browser tab can hold; take a top-holders snapshot of it instead. When the RPC rate-limits the scan, it slows down and retries. A scan that stops before the last account, which can happen on some RPCs and for an NFT collection of more than 100,000 items, is marked Partial and its CSV isn't sold, because holders past that point are missing.

What it costs

Troubleshooting