Research tools
Axiom bundle checker explained
A bundle is a set of buys executed as separate transactions inside the same block, usually by one actor controlling many wallets to grab supply at launch and sell it into later buyers. Axiom's bundle checker flags them with two rules: four or more transactions in one block, and a wallet is only counted if its next transaction is also bundled. The result often differs sharply from other tools, and Axiom says that is by design.
What a bundle looks like on-chain
Solana processes many transactions in each slot. A bundler submits several buys from different wallets so they land together, milliseconds apart, before anyone else can react. Afterwards those wallets hold a large share of supply, which they distribute into the buying that follows a launch or migration. Axiom's FAQ notes that some platforms' warnings are too vague to separate orchestrated buys from normal activity.
Axiom's two detection rules
| Rule | What it does | Why |
|---|---|---|
| Four or more transactions in the same block | Flags the block as a potential bundle | Fewer than four is too easily ordinary market activity |
| Filter out unbundled wallets | A wallet whose next transaction is not part of a bundle is dropped from detection | Removes traders who happened to land in a busy block but do not bundle consistently |
Axiom's own wording is worth keeping: no bundle detection method is 100% foolproof, and some false positives and missed bundles are inevitable.
Why Axiom's bundle % differs from other tools
Axiom's FAQ addresses comparisons with Trench Radar and similar checkers directly. Two differences:
- No time limit. Tools that rely on pump.fun's own flag only detect bundles in the first few blocks after creation. Axiom detects bundles whenever they occur, because a bundle can happen at any point and does not have to come from the deployer.
- Stricter filtering. By ignoring wallets that do not maintain a bundling pattern, Axiom reduces false positives. Its figure may look "wildly different", in Axiom's words, but is meant to reflect the actual risk of trading the token.
In practice this means Axiom's number can be lower than a launch-only tool on a token that was bundled at creation and then widely distributed, and higher on a token that was bundled later by a buyer who was not the team.
How to read the number
| Bundle % | Reading |
|---|---|
| Near 0% | No detected coordinated buying. Says nothing about dev or insider holdings; check those separately |
| Low single digits to about 15% | Some bundling, common on popular launches. Weigh against holders and liquidity |
| High | A large share of supply sits with a coordinated actor who can sell at once. Treat as a dump in waiting unless the wallets have already distributed |
The bundle figure appears as a Pulse filter and on the token page. Read it together with Dev holding, Insiders and Top 10 holders, and then open Trader Scan to see whether the bundled wallets still hold.
What the checker cannot catch
- Supply bought across several blocks rather than one
- Wallets that bundle once and then behave normally, which Axiom deliberately filters out
- Team wallets that were funded before launch and buy singly
- A honest launch that later gets rugged by removing liquidity
Bundle checker FAQ
What counts as a bundle on Axiom?
Four or more transactions in the same block, with wallets dropped from the count if their next transaction is not also bundled.
Why does Axiom show a different bundle % from Trench Radar?
Axiom detects bundles at any time rather than only in the first blocks, and filters out wallets that do not keep bundling. Axiom says this makes its figure a more accurate reflection of risk.
Is a 0% bundle score safe?
No. It means no coordinated block buys were detected. Dev holdings, insiders, liquidity and the team's intentions are separate risks.
Is the bundle checker free?
Yes. It is part of the terminal.
Sources: FAQs (Bundle Checker) and Pulse pages on docs.axiom.trade. Read 5 November 2026.