TALENTRE

Wallet research

Solana bundle checker: how to read the results

Layered paper tickets held in a dark precision clip beside the title Solana bundle checker

A bundle percentage is useful only when you know which wallets it counts and where their tokens went. A Solana bundle checker can help reconstruct the launch, but the trading question is what those buyers still hold and how the checker reached that number.

In this article

Separate launch buying from supply still held

For a concrete starting point, open GlassDex's Solana bundle checker, paste the full mint address and select Scan. Its published method flags creation-block buyers, tracks early snipers separately and reads those wallets' current balances. GlassDex describes this detection as inferred from timing and balances. That classification rule differs from Jito's transaction execution definition below.

Other checkers may use a wider opening window or add wallets connected through funding and transfers. Open the explanation behind the label before comparing results: different methods answer different questions, even when the interface calls every result a bundle.

MeasurementWhat it describesWhat to inspect
Launch purchasesTokens acquired by the selected buyers during a defined opening windowIncluded transactions, window and buyer addresses
Current holdingsBalances held by the selected address set at the latest snapshotUpdate time, owner aggregation and added recipients
Wallet connectionsRelationships used to group addressesFunding or transfer transactions and the grouping rule

Record each separately. Launch purchases describe the initial distribution; current holdings describe the position visible now. A connection explains why an address was included. Combining them into one unexplained percentage loses the information needed to assess the result.

A Jito bundle has a precise technical meaning

Jito defines a bundle as up to five transactions executed sequentially and atomically within one slot. Under bundle execution, the transactions succeed together or none are committed. The limit counts transactions, not wallets or individual instructions.

Several buys in the same block, or with the same displayed timestamp, do not establish that they belonged to one Jito bundle. They also do not establish one controller. If a checker provides a bundle ID and its transaction list, compare those signatures with the purchases it flagged. Jito's bundle-status response can report the member transactions, slot and confirmation status when the record is available; its documented lookup has recent-history limits.

Without that evidence, describe the finding by the rule you actually checked, such as creation-block buyers. This still gives you a useful group to investigate without turning a timing match into a claim about how the orders were submitted.

Reconstruct the purchases behind the label

Copy the full mint address into the checker and verify the network. Save the scan time, detected launch slot and links to the flagged transactions. Establish whether the window begins at mint creation or at the first trading event; those are distinct events, and a tool's coverage may depend on the launch venue.

Open the earliest flagged transaction in an explorer. Check success, the invoked trading program and the token's pre- and post-transaction balances. Match the recipient to a token-account owner. A positive balance change can come from a transfer or initial allocation, so pair it with the swap instruction and payment movement before counting it as a purchase.

Continue through the included transactions, keeping one row per purchase with its signature, slot, owner and token amount. Separate gross buys from the position remaining at the end of the window: buying, selling and buying again creates turnover without creating the same amount of retained supply. Check how the tool handles that distinction before summing its rows.

Count owners and identify reserve accounts

Solana tokens sit in token accounts. A wallet can own several accounts for the same mint; its associated token account, or ATA, is the standard derived account, not necessarily its only one. Aggregate balances by the token account's owner field so that multiple accounts do not become multiple supposed traders.

Keep the fee payer, account-creation payer, token owner and trading-fund source in separate columns. Paying to create another wallet's ATA does not make the payer its owner. Likewise, a wallet receiving SOL from an exchange identifies a funding route, not who controls it.

Identify bonding-curve accounts, pool vaults and other protocol reserves through their program and account roles. Pump's trading documentation, for example, distinguishes the bonding curve's token account from the user's. Remove reserve inventory from the buyer group, while preserving its role in the supply calculation. Do not simply discard every account owned by a program: ordinary SPL token accounts are themselves owned at the Solana account level by a Token Program.

Calculate the percentage on a named denominator

For current holder concentration, divide the selected owners' combined token balances by the stated supply denominator and multiply by 100. Match balances and supply to the same snapshot as closely as the data allows, and retain the reported slots. Use consistent token units; raw amounts and decimal-adjusted balances cannot be mixed.

Solana's getTokenSupply returns the mint's current supply. A dashboard may instead use an adjusted circulating figure or a launch allocation, so record the exact denominator. Excluding a pool from the buyer list does not automatically justify removing its tokens from total supply. If an adjusted calculation excludes reserves from both sides, it needs its own label.

Compare the denominator as well as the wallet list when two checkers disagree. A historical launch percentage and today's concentration can both be correct while answering different questions. An ordinary token transfer changes balances without changing mint supply; minting and burning can change supply, which matters when comparing snapshots.

Follow transfers before marking a buyer as exited

An empty launch wallet has no balance at that address. To establish a sale, inspect the outgoing transaction for a swap and the proceeds received. A transfer to a new wallet is a different event, and a balance reduction alone cannot tell you which happened.

For transferred tokens, retain the destination and the supporting signature. Show current balances at the original buyers separately from balances at traced recipients. A recipient relationship establishes the transfer path; adding that address to a common-control group requires further evidence. Record the rule rather than silently assigning every recipient to the launch team.

Deduplicate the address set before summing current holdings. Count each token account once, then aggregate by owner. Never add the launch purchase amount to the recipients' current balances: that combines historical flow with a current position and can count the same tokens again. Once tokens have mixed with other holdings or passed through a market, avoid pretending that a later balance consists of uniquely identifiable launch tokens.

Turn the scan into a result you can revisit

Save the mint, launch window, selected owners, transaction signatures, exclusions, supply denominator and snapshot time together. Keep three totals where available: purchases during the window, current balances at those buyers and current balances at separately identified recipients. Mark unavailable history as incomplete coverage instead of recording zero.

This gives the next scan a clear purpose. You can see whether the original buyers reduced their positions, transferred tokens onward or bought again, and verify which event changed the percentage. To assess what a retained position could sell for, continue with the market-data checks and slippage versus price impact. A share of token supply and the liquidity available to absorb a sale are separate measurements.

Frequently asked questions

What does bundled mean on Solana?

In Jito's technical definition, a bundle contains up to five transactions executed in order and atomically within one slot. In launch analytics, bundled can instead mean buyers selected by timing or wallet relationships. Check the tool's definition before treating those labels as equivalent.

How do I check whether a Solana token was bundled?

Scan the exact mint address, inspect the flagged launch transactions and record the detection window. Verify purchases through instructions and balance changes, then look for bundle membership evidence where available. Same-block buying alone establishes timing, not a confirmed Jito bundle.

What percentage of bundled supply is safe?

A percentage alone cannot establish safety. First determine whether it measures launch purchases or current holdings, which addresses it includes and what supply it uses. Assess the remaining position alongside executable liquidity and the transactions supporting the wallet grouping.

Does a bundle wallet with zero tokens mean it sold?

No. It may have transferred the tokens. Inspect outgoing transactions for swaps and proceeds, and track transfer recipients separately. A checker that reads only the original wallets can miss tokens held elsewhere after a transfer.

Do Solana bundle checkers work outside Pump.fun?

Coverage depends on the checker and the trading programs it parses. Verify support for the token's actual launch venue, including the available history and detection window. A missing result for an unsupported venue does not establish an unbundled launch.

Can I check bundled supply without connecting a wallet?

Public mint addresses, transactions and account balances can be inspected without signing a transaction. A tool may require an account or paid access for its analysis, but a wallet signature is not necessary to read the underlying public-chain records.

Questions or corrections? Contact the Talentre team.

← All articles