The best Solana bundle checkers in 2026 — and the launch pattern none of them catch

Why you check bundles at all

A "bundled" launch is one where the token creator buys a large slice of their own supply at the moment of creation, using multiple wallets submitted in a single Jito bundle — so all the buys land in the exact same block. It makes the holder chart look organic while one person controls the float. When they sell, everyone who bought after them is the exit liquidity.

The scale of the problem is not in dispute: research from Solidus Labs found that roughly 98.6% of tokens launched on pump.fun showed rug-pull or pump-and-dump characteristics. Checking a launch before buying isn't paranoia — it's the baseline.

The tools, reviewed honestly

The pattern they structurally cannot see

Every tool above answers the same question: "who bought in the creation block?" So the counter-move writes itself, and it's now documented practice in launch tooling:

What actually catches it: the funding graph

The unbundled launch beats same-block detection, but it can't avoid leaving two other traces on-chain:

• The funding lineage. Those "independent" early buyers were seeded from somewhere. Walk each wallet's SOL inflows back through the chain and coordinated wallets collapse into a small set of shared sources — sometimes the deployer itself, one hop removed.
• The early-buyer record. The first buyers of a token are permanent history. Even after the snipers dump and vanish from the holder list, who bought first and who funded them is still sitting there in the ledger.

That second point matters more than it sounds: a holder-based scanner loses sight of snipers the moment they exit — which is exactly when the damage happens. A funding-graph scan of the first buyers, not just the current top holders, keeps the coordination visible after the fact, with the funding transactions as evidence anyone can verify on Solscan.

This is the layer Cabal-Hunter is built around — to be clear about the bias, it's our product. One scan runs the funding trace on top holders and the token's first buyers, plus same-block bundle detection, live coordinated-dump detection and the deployer's full launch history, and returns one verdict with an on-chain evidence transaction attached to every flag:

# one call, no API key, 250 free scans/month
curl "https://api.cabal-hunter.com/api/scan-cabal?mintAddress=<MINT>"

# the part no bundle checker returns:
"clusters": [{
  "type": "early_sniper",
  "wallet_count": 4,
  "bought_pct": 11.2,       // taken at launch
  "combined_pct": 0.3,      // still holding — they already exited
  "evidence_txs": ["5Kd9…"] // the funding transactions, verifiable on Solscan
}]

The honest comparison

The stack we'd actually run

1. Trench Radar for the instant same-block bundle % — it's free and the best at what it does.
2. Cabal-Hunter for the funding graph, the first-buyer trace and the deployer's record — the coordination that same-block tools can't see.
3. RugCheck for contract-level basics (authorities, LP state) — see our side-by-side of RugCheck, Bubblemaps and Cabal-Hunter.

Three tools, three different questions, ~20 seconds total. A launch that passes all three can still rug — nothing prevents a holder from simply selling — but you've eliminated the launch patterns responsible for most of the losses.