Atomic transfers
Compose several transfers into one Solana transaction: all instructions succeed together or all revert. This is not a Jito bundle and does not provide atomicity across transactions.
Each network has a separate transfer plan and receipts. Switching back restores its saved progress.
Recipient list
DevnetFormat: address,amount, one recipient per line. Optional address,amount header. No quotes or extra columns. Up to 100 recipients and 20 KB; exact decimal amounts only. Tokens are sent from your associated token account.
Jito transaction bundles
Build 1–5 signed SOL transfer transactions from up to 20 CSV recipients, submit them as one ordered Jito bundle, and query real relay and chain status.
Mainnet Beta · Real SOL. Jito normally executes a bundle atomically in one slot. Skipped blocks and rebroadcasts can break that protection and expose partial execution. Receipt of a bundle ID does not mean it landed.
Connects directly to Jito’s public Block Engine without an API key. Public requests can be rate-limited or blocked by the browser/network. If unavailable, use the official documentation below for relay options and check saved signatures before any new submission.
Official Jito documentationOfficial documentation opens in a new tab outside this site.
Classic Jito Block Engine minimum: 0.000001 SOL (1,000 lamports). The tip is added to the last business transaction, using a randomly selected account returned by getTipAccounts. The minimum does not guarantee landing.
Look up bundle status
Jito status has a limited lookback. Null or Invalid is not proof that no transaction executed. Saved submissions are confirmed independently using every known signature and Mainnet RPC history. An expired record requires a finalized block height beyond validity and no signatures found.