A Jito bundle explorer shows something a normal Solana explorer does not: which transactions were submitted together as one atomic package, in what order, and how much the sender tipped to get them included. The main tool is Jito Labs’ own bundle explorer at explorer.jito.wtf. Traders use it to check their bundles; researchers use it to spot bundled memecoin launches and MEV. This guide explains bundles and tips in plain language, shows how to read a bundle page, and covers the risks for ordinary users.
What are Jito bundles and tips?
A Jito bundle is a group of up to five transactions that execute sequentially and atomically: in the listed order, and all-or-nothing. A tip is a SOL payment to one of Jito’s tip accounts that pays for the bundle’s inclusion.
Jito Labs builds a validator client and a block engine. Searchers and trading bots send bundles to the block engine, which passes them to validators running the Jito client. The validator includes the bundle in a block only if every transaction in it succeeds, in order. If any one fails, none land. That guarantee is why bundles exist: a trader can do “buy, then sell”, or “create token, then buy”, without the risk that only half the plan executes.
Tips work like an auction for priority. According to the Jito low-latency send docs, there are eight tip accounts, you can fetch the current list with getTipAccounts, and the minimum tip is 1,000 lamports. In busy moments, bots bid far above that. A tip is separate from the normal Solana fee: you still pay the 5,000-lamport base fee per signature and any priority fee, explained in the official fee documentation.
Jito’s docs make one practical recommendation worth repeating: put the tip transfer inside the same transaction that runs your strategy. If that transaction fails, the tip is not paid either.
The Jito Tip Payment program
Tips are handled by the Jito Tip Payment program, T1pyyaTNZsKv2WcRAB8oVnk93mLJw2XzjtVYqCsaHqt, declared in Jito’s open-source jito-programs repository. The eight tip accounts are owned by this program.
T1pyyaTNZsKv2WcRAB8oVnk93mLJw2XzjtVYqCsaHqt
On a normal explorer, a tip appears as a plain SOL transfer from the sender to one of the tip accounts, usually as the last instruction of the last transaction in the bundle. That is the easiest way to recognise a Jito transaction on Solscan or Orb: look for a System Program transfer to an address labelled as a Jito tip account. The program then distributes collected tips according to Jito’s rules for validators and stakers; for how staking rewards reach delegators, see our validator and staking explorer guide.
If you want to inspect the program itself, open it like any other contract. Our program explorer guide explains the upgrade authority, program data account and verified-build fields you will see.
How to use the Jito bundle explorer at explorer.jito.wtf
The Jito explorer lists recent bundles and lets you search by bundle ID. Each bundle page shows the transactions in order, the tip, the slot and whether it landed.
A typical check goes like this:
- Get the bundle ID. When a bot or SDK sends a bundle, the block engine returns a bundle ID, a long hex string. Many trading tools show it in their logs.
- Search it on explorer.jito.wtf. Paste the ID into the search. A freshly landed bundle can take around a minute to appear.
- Read the transaction list. Transactions appear in execution order. The last one usually contains the tip transfer.
- Open each transaction. Every row links out so you can read instructions and token balance changes on a regular explorer, or paste the signature into our lookup tool.
For bundles that have not landed yet, the block engine’s getInflightBundleStatuses method reports status for the last five minutes, and getBundleStatuses confirms landed bundles with their slot. If a bundle never appears, the most common reasons are a tip too low for current competition, one transaction failing (which drops the whole bundle), or an expired blockhash; blockhashes stay valid for 150 slots. Our transaction explorer guide covers how to diagnose the failing transaction itself.
How memecoin traders use Jito bundles
Memecoin traders use bundles for speed and certainty: to be first into a new token, to buy with several wallets in the same instant, or to buy and sell in one atomic package.
The most common pattern is the launch bundle. A creator deploys a token on a launchpad such as pump.fun (program 6EF8…wF6P) and, in the same bundle, buys from several wallets they control. Because the bundle is atomic, nobody else can buy between the creation and those purchases. The creator ends up with a large share of supply at the lowest price, spread across wallets so it looks like organic demand.
Sniper bots use bundles too, to buy in the first block after a pool opens. Arbitrage bots use them to trade across two DEX pools without the risk of one leg failing. None of this is hidden: it all lands on chain, which is why a bundle explorer is useful.
How to spot a bundled launch
A bundled launch leaves a clear fingerprint: token creation and a burst of buys from different wallets in the same slot, with a tip transfer to a Jito tip account at the end.
To check a token yourself, open its mint on Solscan or Orb and sort its activity from oldest to newest. Then ask:
- Did several buys land in the same slot as the creation? Organic buyers rarely manage that. A bundle does it by design.
- Is there a transfer to a Jito tip account in those first transactions? That confirms a bundle was used.
- Were the buying wallets funded from one address shortly before? Open two or three of them and look at their first incoming SOL. The wallet explorer guide shows how to trace funding.
- How much supply do those wallets hold now? If they still hold a large share, they can sell together.
You can also search the first transaction’s signature on explorer.jito.wtf to see the full bundle. Trading terminals often flag bundled supply; our DeFi and DEX explorer guide compares the tools that surface it. A bundled launch is not always a scam, but it tells you the creator’s side started with an advantage.
Warning: A chart can look healthy while a handful of bundled wallets hold most of the supply. Check the first slot of the token's history before you buy, not after.
MEV risks for ordinary users
MEV (maximal extractable value) is profit taken by reordering, inserting or censoring transactions. For a normal user on Solana, the risk that matters most is the sandwich attack on a swap.
In a sandwich, a bot sees your pending swap, buys just before you, lets your trade push the price up, and sells right after. You get a worse price, up to your slippage limit. Jito Labs suspended its public mempool in March 2024 because of this, which removed one route for sandwiching, though other private channels have appeared since.
What you can do:
- Keep slippage as tight as the pool allows, especially on thin memecoin pools.
- Use a wallet or DEX front end that offers MEV protection or private routing.
- Split large orders, or use a limit order instead of a market swap.
- After a bad fill, open your transaction and the ones directly before and after it in the same slot. A buy just before and a sell just after from the same wallet is a sandwich.
IBRL and the Jito IBRL Explorer
IBRL stands for “Increase Bandwidth, Reduce Latency”, a motto used across the Solana ecosystem for its performance goals: more throughput and faster confirmations. Solana’s own writing on slot-time cuts and Alpenglow frames them this way.
The phrase also names a tool. The IBRL Explorer at ibrl.wtf launched in January 2026 and points feedback to Jito’s developer channels. It scores validators on block-building quality using public chain data: slot time, vote packing and non-vote packing, combined into a weighted score. That is a different question from bundles: not “what did this trader do?” but “how well does this validator pack blocks?”.
It fits the bigger picture. Slot times are dropping in steps under SIMD-0525, from 400 ms toward 200 ms, and current slots run at about 250–300 ms. For live throughput and slot numbers, see our Solana network stats page.
Using the Jito bundle explorer alongside Solscan and Orb
Use explorer.jito.wtf for the bundle view and a general explorer for everything inside it. The two work together.
The Jito explorer tells you what was grouped, in what order, and what was tipped. Solscan, Orb and Solana Explorer tell you what each transaction did: which programs ran, which tokens moved and what the logs say. For most people, Orb’s plain-language summaries make bundle transactions easier to read, while Solscan’s labels help identify tip accounts quickly. Our ranking of the best Solana explorers compares them on speed, token data and readability.
A good habit when something looks off: start from the token or wallet on a general explorer, find the suspicious slot, and only then jump to the Jito explorer with the first signature to see whether it was part of a bundle. Working in that direction keeps you anchored to facts you can verify, such as balances and mint addresses, instead of starting from a bot’s bundle ID you cannot interpret yet. If you want a friendlier reading of each transaction inside a bundle, our Orb review shows how its AI summaries and spam filtering help with busy memecoin wallets. And if the bundle explorer is slow or will not load, check again after a few minutes: new bundles appear with a short delay, and a missing bundle is more often a dropped bundle than a broken site.
By the Solscanner research deskUpdated · Review methodology