Explainer · MEV
MEV, explained
October 8, 2026
Every on-chain trade pays a network fee that's visible on the receipt. Fewer people know about the second cost that can sit on top of it — extracted by someone else, simply because the trade was visible before it confirmed. That's MEV: not a bug, not a scandal exclusive to crypto, but a structural feature of how public blockchains order transactions.
Why a trade is visible before it confirms
An on-chain transaction doesn't confirm instantly. It sits briefly in a public waiting area called the mempool — visible to anyone running a node — while it waits to be included in the next block. Whoever builds that block also chooses the order the pending transactions inside it are arranged in.
Those two facts together are what make MEV possible: public visibility before confirmation, and control over ordering. Neither one is a flaw. Both are necessary for a public blockchain to work at all.
What MEV actually is
MEV stands for maximal extractable value — the extra profit available from inserting, reordering, or excluding transactions within a block, beyond the block's normal reward. Specialized participants known as searchers scan the visible mempool for profitable opportunities, most often a large pending trade about to move a price, and pay to have their own transaction placed favorably around it.
It isn't theft in a legal sense; every step uses the network exactly as designed. It's closer to a structural information edge — available to whoever is fastest and best-equipped to act on what's already public.
The sandwich attack, step by step
- The setup. A trader submits a swap on a decentralized exchange. The order sits briefly in the public mempool before it confirms.
- The front. A searcher sees it and places a buy order just ahead of it, pushing the price up slightly before the original trade executes.
- The squeeze. The original trade goes through at that now-worse price — the trader paid more than the market showed a moment earlier.
- The back. The searcher immediately sells what it just bought, at the higher price the original trade helped create, pocketing the difference.
Structural, not a bug — and what limits it
This isn't a flaw nobody patched. Public blockchains are transparent by design, and that transparency is what makes them auditable and trustworthy in the first place. The same openness that lets anyone verify a transaction also lets anyone see it coming before it confirms. MEV is the cost side of that transparency, not a separate mistake sitting on top of it.
A few real approaches reduce exposure without changing that tradeoff. Private transaction routing submits a trade without it ever passing through the public mempool, leaving nothing for a searcher to see in advance. Some networks and tools now auction ordering rights more fairly or redirect part of the resulting value back to ordinary users rather than only to searchers. And setting tighter slippage tolerance — the maximum price movement a trade will accept — limits how much a sandwich attack can cost even when one still happens.
The read
MEV isn't a scandal exclusive to crypto — it's the on-chain version of an information edge that exists in every visible market, made unusually explicit because the system is transparent by design. It shows up most in DEX trading, where a pending swap sitting in the mempool is the clearest signal a searcher can act on. Knowing it exists, and setting slippage tolerance accordingly, is ordinary practical literacy for anyone trading on-chain — not a reason to avoid it.
This is general-circulation educational content, not investment or legal advice. MEV mitigation tools and their availability vary by network and change over time; this piece describes the mechanism, not a specific product recommendation.
For how a DEX trade executes end to end, see Blockchain IQ's explainers on DeFi and CEX vs. DEX.