Solana Token Holder Snapshot

A holder snapshot is a list of every wallet that holds a given token at one moment, together with how much each wallet holds. On Solana the list is assembled from token accounts: each wallet that has received the token owns a token account for that mint, and the account stores the balance. A snapshot scans those accounts, groups them by owner, and records the sum.

The word snapshot matters. Balances move every second on a live token, so the list is only true for the instant it was taken. Any decision that depends on it, such as who qualifies for an airdrop or how many votes a wallet carries, should be pinned to that instant and announced in advance so nobody can game it by moving tokens afterwards.

This page gives you that list without an indexer, an RPC subscription, or a script. The same holder scan powers the Token holders recipient source in the DexLab Multisender; here it stands on its own so you can inspect and export the list before you send anything.

Most teams need a holder list at four moments in a token’s life:

• Airdrops and rewards. A community airdrop, a loyalty reward, or a retroactive distribution all start from the question of who held the token on a given day. Take the snapshot, apply a minimum balance so dust wallets are left out, and hand the list to the Multisender.
• Governance. A vote weighted by balance needs a fixed voter list. Taking the snapshot at the announced block or time freezes the weights, so a wallet cannot borrow tokens for the vote and return them afterwards.
• Migrations. When a token moves to a new mint, for example from a classic SPL mint to a Token-2022 mint with transfer fees or metadata extensions, the old holder list is the exact list of wallets that should receive the new token, in proportion to what they held.
• Launch pools and listings. Before you seed a liquidity pool or apply for a listing, the holder count and the concentration of the top wallets are the numbers reviewers ask for. The top 10 and top 50 shares shown above are those numbers.

In every case the snapshot is a record you keep. Download the CSV at the moment you take it, because the live list will have changed by the time you come back.

Solana does not store a balance on the wallet itself. For each mint a wallet holds there is a separate token account, usually the associated token account derived from the wallet and the mint, that records the amount. A wallet can own extra token accounts for the same mint, which is why the tool sums every account per owner rather than counting accounts. Holders is the number of distinct owners with a positive balance.

Amounts on chain are integers in the smallest unit, called base units. The mint declares a number of decimals, and the human balance is the raw amount divided by ten to that power. A mint with nine decimals stores 1.5 tokens as 1,500,000,000. The tool reads the decimals from the mint account itself, so the balances in the table and in the CSV are converted with the same decimals the transfer instructions use, and the CSV carries both the human balance and the raw base units so a script does not need to know the decimals at all.

Token-2022 mints are handled the same way. The tool inspects which program owns the mint account, the classic SPL Token program or Token-2022, and shows it next to the summary. Extensions such as transfer fees or transfer hooks do not change a wallet’s balance, so they do not change the snapshot; they matter later, when you send, and the Multisender handles them with the transfer-checked instruction of the detected program.

Accounts with a zero balance are dropped before grouping, so a wallet that once held the token but sold everything is not listed as a holder.

The Download CSV button produces a plain UTF-8 file with a header row and one row per holder, largest balance first, in the order the table shows after your minimum-balance filter. The columns are:

• rank: position in the list, starting at 1.
• owner: the wallet address that owns the token accounts, in base58. This is the address you airdrop to, not the token account address.
• balance: the human amount, converted with the mint’s decimals and written without an exponent or trailing zeros.
• raw_balance: the same amount in base units, as an integer.
• share_percent: the wallet’s share of the total held by every wallet in the snapshot, to four decimal places.

The export is never trimmed. The table on this page draws at most 1,000 rows, because a list of ten thousand linked wallets is a page that will not scroll on a phone, but the CSV holds every holder left after your filter.

The file name carries the first eight characters of the mint and the date. Because the export uses the same holder list the Multisender loads, a CSV from here can be trimmed in a spreadsheet, given an amount column, and uploaded to the Multisender as a recipient file.

Five limits shape what a snapshot from this tool can and cannot tell you:

• Point in time. The list is true for the moment the chain was read. Take the CSV then, and record the time shown under the summary.
• 60 minute cache. The DexLab API caches each mint’s holder list for 60 minutes. Pressing Take snapshot again inside that window returns the same list, which is why the tool never polls. If you need a fresher list, wait for the window to pass.
• Scan cap of 10,000 token accounts. The scan reads up to 10 pages of 1,000 accounts and stops. A mint with more accounts than that is marked as capped, and the tool says so above the table. Those pages are walked in the order the RPC hands them over, which is not an order of balance, so a capped list is a large sample of the holders rather than a ranking of the biggest ones. For a token with hundreds of thousands of holders, do not treat a capped result as a census or as a top-holder list.
• Whole numbers only up to a point. Balances travel from the API as JSON numbers, which are exact only below about nine quadrillion base units. A nine-decimal token passes that line at roughly nine million tokens, and a balance above it is rounded in its last few digits. The rounding is far below anything a distribution would notice, but it is why raw_balance should be read as an accurate amount rather than a byte-for-byte copy of the chain.
• No pool or program filter. The API does not label which owners are liquidity pools, vaults, or other programs, and this tool does not guess. Large pool and exchange wallets usually sit at the top of the list; remove them by address in the CSV if your airdrop should exclude them.

None of these limits involve your wallet. Reading holders is a public query; nothing is signed and nothing is sent until you choose to airdrop.

The Airdrop to these holders button opens the DexLab Multisender with the same mint selected and the Token holders recipient source already chosen. There you connect the wallet that will send, choose an amount per holder or a total to split in proportion to balances, and press Load holders. The minimum balance you typed here travels with the link and arrives in the Multisender’s own minimum balance field, where you can raise it, lower it, or clear it before you load. The Multisender fills the recipient list, leaves your own wallet out, and runs a pre-flight check that counts how many recipients still need a token account and estimates the network cost.

On Solana mainnet the Multisender service fee is simple. The first 20 recipients are free, each recipient after that costs 0.001 SOL, and a single batch never pays more than 0.3 SOL. Network fees and the rent for any new token accounts are paid to Solana on top, by the sending wallet. Devnet sends are free entirely, so you can rehearse a distribution before spending anything.

To send a different token than the one you snapshotted, for example a reward token to the holders of your main token, download the CSV here, keep the owner column, add an amount column, and upload the file to the Multisender instead.

Read the airdrop guide