MEV Shield
Network-based MEV risk analysis
On-Chain MEV Data
Transaction Sandbox
Enter a transaction signature (e.g., 5abc...xyz) or paste raw transaction JSON
MEV Attack Types
Sandwich Attack
HIGHAttacker places orders before and after victim's transaction to profit from price movement.
Front-running
MEDIUMCopying and executing a profitable transaction before the original sender.
Back-running
MEDIUMPlacing a transaction immediately after a large trade to capture arbitrage.
Liquidation
LOWMonitoring DeFi positions to profit from liquidation opportunities.
MEV Education & FAQ
MEV refers to the maximum value that can be extracted from block production beyond standard block rewards and gas fees. On Solana, this typically involves validators or bots reordering, inserting, or censoring transactions within a block to capture profit at the expense of regular users.
MEV can result in: (1) Higher costs - you may pay more than expected for swaps, (2) Failed transactions - your transaction might fail if conditions change, (3) Worse prices - sandwich attacks can move prices against you. The impact is most significant for large DEX trades during high network activity.
A sandwich attack occurs when a bot detects your pending swap, places a buy order before yours (front-run), waits for your transaction to execute (pushing the price up), then immediately sells (back-run). The attacker profits from the price difference while you receive a worse price than expected.
Key protection strategies: (1) Use private RPC endpoints that don't broadcast to public mempools, (2) Set appropriate slippage tolerance (0.5-1% for most trades), (3) Use DEX aggregators with MEV protection like Jupiter, (4) Split large trades into smaller chunks, (5) Avoid trading during high congestion periods.
For most trades, 0.5-1% slippage is recommended. Lower slippage (0.1-0.3%) may cause transaction failures but offers better protection. Higher slippage (2-5%) increases MEV risk but ensures execution. For volatile tokens or low liquidity pairs, higher slippage may be necessary.
Private RPC endpoints send your transactions directly to validators without broadcasting to public mempools. This prevents MEV bots from seeing and front-running your transactions. Services like Jito, Helius, and dedicated validator connections offer this protection.
Unlike Ethereum, Solana doesn't have a traditional mempool due to its leader-based consensus. However, MEV still exists through: (1) Transaction propagation delays, (2) Parallel transaction processing, (3) Priority fees affecting ordering. Solana's speed actually reduces some MEV opportunities but creates others.
Jito is a MEV infrastructure on Solana that provides: (1) Bundle transactions - group transactions atomically, (2) Backrun auctions - redirect MEV to users/protocols, (3) Private transaction sending. Using Jito-enabled wallets and DEXes can significantly reduce MEV exposure.
High congestion creates more MEV opportunities because: (1) Transaction queues are longer, giving bots more time to analyze, (2) Priority fee competition makes ordering manipulable, (3) Price volatility increases during congestion, (4) Failed transactions create additional arbitrage opportunities.
Understanding MEV is the first step to protecting your transactions