How to check if a pump.fun token was bundled or sniped
The first seconds after a pump.fun token is created tell you a lot about who got in before anyone could react. Two words come up constantly in trader chats: bundled and sniped. This guide explains what they mean on-chain, how to check them yourself on a block explorer, and how to read the same facts on a free BotSharper token sheet. It describes what already happened on a token. It does not tell you what will happen next.
What "bundled" and "sniped" mean on Solana
Solana groups transactions into blocks, each tied to a slot, a fraction of a second apart. On pump.fun, the token is created by one transaction, and the creator can buy in that same transaction. Everything else is about who bought right after.
- Bundled launch: several buys land in the very block where the token was created, usually from several different wallets. They are often submitted together (for example as a Jito bundle, a group of transactions executed in order in one block) and the wallets are frequently funded from a common source shortly before launch.
- Sniped launch: automated buyers pick up the token in the first moments after creation. Definitions vary between data providers. Mobula, for example, defines a sniper as "a wallet that purchases tokens within the first few blocks (typically 0-3 blocks) after a token launches".
Why does it matter? BotSharper's token page states it plainly: "Buying in the very block where the token was created requires advance notice or automation: a human has no time to react." If you bought by hand, the birth-block buyers were already in before you saw the token.
How to check it manually on Solscan
You can verify all of this yourself with a free block explorer.
- Get the mint address. This is the token's address (the "mint"), not a wallet. It appears in the pump.fun page URL and on the token page.
- Find the creation transaction. Open the mint on Solscan and go to the oldest activity for the token. Note its slot (block number) and its time. Note the creator address as well.
- List the birth-block buyers. In the token's trading activity, keep the buys whose slot equals the creation slot. Leave out the creator's own buy, which can sit in the creation transaction itself.
- Widen the window. Repeat for buys within the first second and the first ten seconds, using the block time of each transaction.
- Look at the funding. Open each early buyer and check where its SOL came from just before launch. Several fresh wallets funded by the same address is the classic bundle pattern.
- Check what they did next. On each early wallet, filter by the token to see whether it has already sold.
The main difficulty is volume: a popular launch can have dozens of transactions in its first seconds, and explorers show block times rounded to the second.
What a BotSharper token sheet shows
Paste the mint address on the token check page. The sheet is computed from public on-chain data and, according to the site, updated every hour. It contains these lines:
| Line on the sheet | What it answers |
|---|---|
| Birth | When the token was created, or "before our observation started" |
| Buyers in the birth block (excluding creator) | How many buyers landed in the creation block |
| Buyers in the first second | How many bought within one second of birth |
| Buyers in the first 10 seconds | How many bought within ten seconds |
| Creator | What the creator address bought and sold, in SOL |
| Share of the 5 largest buyers (first 5 minutes) | How concentrated early buying was |
| Migration to PumpSwap | Whether and when the token migrated, or "not observed" |
| Buyers present in our report | How many buyers are ranked in the BotSharper wallet report, and how many sit in the top and bottom fifth |
The sheet carries its own reading note: "Several buys in the birth block point to purchases prepared in advance or automated." The site describes the free Telegram bot @BotSharperBot simply: "send any Solana address".
When the token was born before BotSharper started observing it, the birth, first-second and creator lines cannot be filled in, and the sheet says so instead of guessing.
How to read the numbers without over-reading them
- Zero birth-block buyers is not proof of a fair launch. Coordinated wallets can just as well buy one block later. Look at the first-second and ten-second counts too.
- Many birth-block buyers is not proof of one person. They may be independent bots racing each other. BotSharper's limits page is explicit: "We do not know who is behind an address. One person may hold several; one address may be run by a program or by a group."
- Early arrival is a fact, its cause is not. On the same page: "Top operators often act in groups. We measure that they arrive early, without being able to say whether that is a coordinated fleet or privileged access to information."
- It is not a verdict on the token. The sheet itself says: "This describes what already happened on this token in our data. It is neither a forecast nor advice."
Known limits
If a token is missing, the sheet reads "Token not in our data", followed by the date observation started. BotSharper's rule is to never write "there is none", only "we did not find it in this source". A missing token is not evidence of anything. The full list of what the measure cannot see is on the What we don't know page, and the way the data is built and checked is on the Method page. To see where a particular early buyer ranks among measured operators, paste its address in the wallet report.
FAQ
What is a bundled launch on pump.fun?
A launch where several buys, usually from different wallets, land in the same block as the token's creation. Buying that early requires preparation or automation, because no human can react inside the creation block.
Can I check birth-block buyers for free?
Yes. You can do it by hand on a block explorer such as Solscan by comparing slots with the creation transaction. The BotSharper token sheet shows the count directly, free on the website and through the Telegram bot @BotSharperBot.
Does a bundled launch mean the token will go to zero?
No conclusion about the future can be drawn from it. A birth-block count describes how the launch happened. BotSharper gives no forecast and no advice, and names no asset to buy or avoid.