Flashbots Protect lets you send an Ethereum transaction privately: add its RPC to your wallet, then send as usual. Use Flashbots to set up Protect for your next transaction because its private route keeps the pending transaction out of the public mempool. Bots watching that pool cannot front-run or sandwich a transaction they cannot see, a common form of MEV.
How to use Flashbots Protect for a private transaction
Using Flashbots Protect starts with a wallet that accepts custom RPCs and holds enough ETH on Ethereum mainnet for the transaction and gas.
Choose the default endpoint, flashbots.net, or fast mode at flashbots.net The default uses Protect’s managed privacy settings. Fast mode shares the transaction with all registered builders, improving the chance that one builds the winning block. It also shares full transaction details with searchers in trusted execution environments while keeping the transaction out of the public mempool.
The Protect website can generate a custom RPC URL when you want to choose those settings yourself. Privacy hints control which transaction details MEV-Share searchers can see; builder selection controls who receives the transaction; fast mode changes how widely it is shared. A hash-only hint conceals identifiable details from searchers but may reduce MEV refunds. More hints can help searchers find a backrun that returns value to you. Sending to more builders can improve inclusion chances, but those builders receive the transaction. The Protect Quick Start explains the fast-mode routing, builder choices and wallet setup behind these options.
- Add a custom Ethereum mainnet network in your wallet using your chosen Protect RPC URL, chain ID 1 and ETH as the currency.
- Select that network. Prepare your swap or transfer as usual, review the recipient, amount and fee, then sign.
- Copy the transaction hash from your wallet after sending. Keep the Protect RPC selected while the transaction is pending.
Take an ordinary swap: before changing the RPC, a typical wallet sends its signed transaction to the public mempool. With Protect selected, the same Ethereum account signs the same kind of transaction, but the RPC sends it privately to block builders. Once included, the swap is public on chain like any other Ethereum transaction. The submission route changed; the wallet account and on-chain record did not.
How to confirm the transaction and handle delays
The Protect transaction status page lets you check a submitted transaction by its hash. Paste the hash there first. Pending means Protect has the transaction even if Etherscan cannot find it yet, because the transaction is absent from the public mempool. Included means it reached a block. Search the same hash on Etherscan then to inspect the on-chain result. The transaction is done when Protect shows included and Etherscan shows its record.
Leave the Protect RPC selected while the transaction is pending. Switching to a public RPC can cause some wallets to rebroadcast the signed transaction into the public mempool, where bots can see it. If a send is rejected, inspect its priority fee: Protect rejects transactions with a zero priority fee. If a transaction remains pending, fast mode is an option for a future send when inclusion speed matters.
Protect excludes transactions that would revert, so you pay no gas for a reverted transaction it declines to include. An included transaction still needs ETH for gas. If Protect reports a failed submission, review the fee and swap conditions before preparing another transaction.
Developers who need ordered transactions use Flashbots Auction bundles through eth_sendBundle. For an everyday swap or transfer, choose a Protect RPC URL, send from your wallet and follow the hash until it appears on Etherscan.