Ethereum MEV Explained: Transaction Ordering, Block Builders, and User Risks

Maximal extractable value (MEV) is value that can be extracted from block production beyond the standard block reward and gas fees by including, excluding, or changing the order of transactions. It is not a single fee charged to every user, and it does not mean every transaction is watched or attacked. Its effects depend on the transaction, the route used to submit it, and how a block is built.

What MEV covers

The term was first called miner extractable value when Ethereum used proof of work. After The Merge, validators took over block proposing, so the broader term maximal extractable value became standard. Searchers look for profitable opportunities; block builders arrange transactions and bundles; the selected validator proposes the block. The parties may share the value through bids and fees, but a searcher does not automatically control a block’s final order.

MEV can involve including, excluding, or changing the order of transactions. The label covers different outcomes, from price arbitrage to harmful front-running. It is useful to name the mechanism instead of treating all MEV as one kind of user loss.

Three examples with different effects

Arbitrage: A token can trade at different prices across pools. An arbitrage trade may bring those prices closer, while the bot earns the difference. This can improve price alignment, but it is still a competitive use of transaction ordering and is not automatically beneficial to every trader.

Liquidations: Lending protocols can let liquidators repay or close positions that no longer meet collateral rules. Liquidation incentives help protocols handle under-collateralized debt, while the borrower may lose collateral and liquidators compete to act first.

Sandwich attacks and front-running: A searcher may use a pending public swap to place a trade before it and another after it, changing the price the original trader receives. The attack depends on the particular swap and its ordering; it is not a description of every transaction or every searcher.

Pending transactions can follow different routes

There is no single queue that gives every Ethereum participant a complete view of all pending transactions. Nodes keep local mempools, and transactions sent through public network routes may become visible to searchers. Some wallets and applications also offer private transaction routes that send a transaction to a provider or builder without first broadcasting it through the public mempool.

A private route can reduce exposure to public-mempool front-running, but it shifts trust to the route’s provider and its connected builders. The provider’s privacy settings, routing, and inclusion policy matter; “private” does not mean a transaction is hidden from every party or guaranteed to land in a block.

What MEV-Boost changes

Flashbots built MEV-Boost as open-source middleware that validators can run to access external block builders. Builders assemble candidate blocks and submit bids. Relays can connect builders with validators, check and route bids, and provide block data. A validator can select a bid and propose the resulting block.

This is an implementation of proposer-builder separation outside Ethereum’s consensus protocol; it is not the same as protocol-native PBS. Separating block building from proposing can let validators use specialized builders, but it does not remove MEV. Relays and builders also introduce trust, availability, and concentration questions. The design and the operators connected to it affect how those trade-offs play out. Validators can configure more than one relay, but a relay still handles bids and block data before a proposer signs. This means trust and availability depend on the chosen operators and configuration as well as on the software.

What the criticism gets right—and what it misses

Calling all MEV harmful is too broad. Arbitrage can bring prices across pools closer, and liquidation incentives can help lending protocols address under-collateralized positions. Those functions do not guarantee that affected users receive the gains, and they do not make sandwich attacks harmless. The result depends on the strategy and whose outcome is measured. Likewise, an external builder market changes who assembles blocks and introduces dependencies; its existence alone does not prove that Ethereum is either fully centralized or unaffected by concentration risk.

What users can and cannot control

For a swap, a slippage limit can cap how far execution may move from the quoted price before the transaction reverts. That can make some sandwich attempts less attractive, but a setting that is too tight can also cause an ordinary trade to fail. Transaction size, liquidity, timing, and the application’s routing all matter.

Some applications use private transaction routing or batch auctions. For example, CoW Protocol groups trade intents into batches and its solvers first look for orders that can match each other before sourcing other liquidity. That changes how some orders reach the chain; it is not a universal guarantee against losses, failed execution, or every form of MEV.

Why MEV totals need context

A reported MEV total can mean the gross value available to searchers, the revenue captured by a searcher or builder, a validator’s bid, or an estimate of harm to traders. Those figures are not interchangeable. Research should be read with its period, data coverage, and definition in view; a historical DEX measurement is not a current total for all Ethereum activity.

MEV is best understood as a set of incentives around transaction inclusion and ordering. Some strategies can align prices or help lending protocols process liquidations; others worsen a user’s execution. MEV-Boost changes how block-building work is organized, while privacy routes and execution designs offer different trade-offs rather than a complete fix.

Related Articles

Related Glossary Terms

See Also

Sources