> ## Documentation Index
> Fetch the complete documentation index at: https://blog.blockdb.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What Is Maximal Extractable Value (MEV) in Ethereum and How Does It Work?

> MEV is the profit block builders and searchers extract by controlling transaction ordering within a block. This guide explains the mechanics, types, key players, and economic consequences - from first principles.

<div className="w-full overflow-hidden rounded-xl mb-8" style={{ maxHeight: '420px' }}>
  <img src="https://mintcdn.com/blockdb-24509496/3_19XeWTBFiGQswV/images/posts/mev-ethereum-explained.png?fit=max&auto=format&n=3_19XeWTBFiGQswV&q=85&s=926f1aa1498a6c44f953d3e11e93bd61" alt="MEV in Ethereum - block ordering, searchers, and front-running explained" className="w-full object-cover" width="1536" height="1024" data-path="images/posts/mev-ethereum-explained.png" />
</div>

<div className="flex flex-wrap items-center gap-3 mb-8 text-sm text-gray-500">
  <span>Mar 4, 2026</span>
  <span className="text-gray-300 dark:text-gray-700">·</span>

  <span className="inline-flex items-center gap-1">
    <svg width="12" height="12" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" aria-hidden="true">
      <circle cx="12" cy="12" r="10" />

      <path d="M12 6v6l4 2" />
    </svg>

    9 min read
  </span>

  <span className="text-gray-300 dark:text-gray-700">·</span>
  <span className="text-xs px-2.5 py-0.5 rounded-full bg-gray-100 text-gray-500 dark:bg-white/[0.06] dark:text-gray-400">#MEV</span>
  <span className="text-xs px-2.5 py-0.5 rounded-full bg-gray-100 text-gray-500 dark:bg-white/[0.06] dark:text-gray-400">#Ethereum</span>
  <span className="text-xs px-2.5 py-0.5 rounded-full bg-gray-100 text-gray-500 dark:bg-white/[0.06] dark:text-gray-400">#DeFi</span>
</div>

Every block on Ethereum is a market. The 12 seconds between when your transaction enters the
mempool and when it lands on-chain is a window in which specialized actors - searchers, block
builders, validators - can reorder, insert, or suppress transactions to extract profit at your
expense. That profit has a name: Maximal Extractable Value.

This article covers what MEV is, where it comes from, who extracts it, and why it matters for
anyone building or trading on DeFi infrastructure.

## Definition

**Maximal Extractable Value (MEV)** is the additional profit that can be captured by
controlling the ordering, inclusion, or exclusion of transactions within a block. It is not gas
revenue - it is value extracted on top of the standard block reward by structuring the block's
transaction sequence to exploit on-chain price inefficiencies.

The mechanism is straightforward: because blockchain transactions are publicly visible in the
mempool before they are confirmed, actors with the ability to influence block construction can
react to, front-run, or sandwich pending trades.

MEV is structurally identical to several well-understood strategies in traditional finance:
front-running a client order, capturing a liquidation at a discount, or exploiting a latency
mismatch between two exchanges. The difference is that on-chain, this is embedded in the
protocol itself - not a compliance violation, but a feature of how blocks are built.

## Historical context: from Miner to Maximal

The term was coined as **Miner Extractable Value** in the 2019 academic paper *Flash Boys 2.0*
by Daian et al., which documented how Ethereum miners could reorder transactions within a
block to capture arbitrage profits on decentralized exchanges. At the time, miners controlled
block construction directly under Proof-of-Work.

When Ethereum transitioned to Proof-of-Stake in September 2022 (the Merge), the role of
miners was replaced by validators. But validators in the new architecture do not build blocks
directly - they select from pre-built blocks submitted by specialized **block builders**. This
structural shift moved MEV extraction from miners to a new class of actors, and the term was
updated to **Maximal** Extractable Value to reflect that the theoretical maximum can be
captured by any participant in the pipeline - not just the block producer.

Two developments mark the post-Merge MEV landscape:

1. **Proposer-Builder Separation (PBS)** became the dominant architecture. Block construction
   and block proposal are now separate roles, with builders competing to offer the most
   profitable block to validators.
2. **Private transaction channels** (Flashbots and its successors) created a parallel routing
   layer that lets searchers submit transaction bundles directly to builders, bypassing the public
   mempool.

## Key players

### Searchers

Searchers are the front-line MEV actors. They scan the mempool continuously using automated
bots, looking for profitable opportunities: price discrepancies between DEXs, pending large
swaps that will cause slippage, undercollateralized positions approaching liquidation thresholds.

When a searcher identifies an opportunity, they construct a transaction (or a bundle of
transactions) timed precisely to exploit it, paying a premium gas fee to maximize the chance
of inclusion at the right position in the block. The market is highly concentrated: around 20
teams dominate MEV extraction, with an estimated total of \~500 active searchers deploying
over 2,800 bots on Ethereum, according to EigenPhi research from 2023.

### Block builders

Block builders aggregate transactions from the public mempool and from private submission
channels (including bundles sent by searchers). Their job is to construct the most profitable
block possible by selecting and ordering transactions to maximize total fees plus MEV
extraction.

Block builders do not propose blocks - they bid for the right to have their block proposed.
The market is extremely concentrated: as of 2024, six builders control the majority of block
production on Ethereum.

The analogy from traditional finance is the high-frequency trading firm or dark pool operator:
entities who structure order flow privately and then present the result to an execution venue.

### Validators (block proposers)

Under PBS, validators receive pre-built block candidates via a relay layer (MEV-Boost) and
select the one with the highest bid. They do not see the transaction ordering inside the block
before accepting it - they only see the header and the bid value.

Validators capture MEV indirectly: through the bid premium builders pay to have their block
accepted. This has made MEV a meaningful component of validator revenue, alongside base
block rewards and priority fees.

### The relay

Relays are trust-minimized intermediaries between builders and validators. They verify that
a builder's block is valid and hold the block contents confidential until the validator commits
to proposing it. This prevents validators from stealing MEV by observing the block contents
and recreating the transactions themselves.

## How MEV extraction works: the mechanics

The extraction pipeline has five stages:

**1. Identification.** MEV bots and searchers scan the public mempool for actionable signals:
a pending large swap that will push a pool's price, a position on Aave crossing its
liquidation threshold, a price divergence between Uniswap and Curve.

**2. Bundle construction.** The searcher constructs one or more transactions designed to
capture the opportunity - typically a front-run, a back-run, or both (sandwich). These
transactions are bundled together with ordering constraints and submitted to builders directly
or via private channels like Flashbots Protect.

**3. Block construction.** The block builder receives bundles from multiple searchers and must
solve an optimization problem: which transactions to include, in what order, to maximize the
block's total value. This includes the option to exclude competing searcher transactions to
ensure their own (or a preferred searcher's) bundle executes successfully.

**4. Block proposal.** The completed block is submitted to validators via relays. Validators
select the highest-bid block without knowing its contents, and propose it to the network.

**5. Execution.** The block is added to the chain. MEV profits are realized at the moment
of execution: the searcher's transactions settle at the favorable price, and the profits are
distributed between the searcher, the builder (via direct inclusion), and the validator (via
the bid).

Timing is the dominant constraint at every stage. On Ethereum, a block is produced every
12 seconds. For "next block" MEV, the entire cycle - identification, bundle submission,
block construction, validator selection - must complete within that window.

## Types of MEV

### Arbitrage

Price discrepancies between DEXs arise because each pool updates its price only when a swap
is executed within that pool. Between two confirmations, Uniswap and Curve may show
different prices for the same token pair.

Arbitrage bots exploit this by buying on the cheaper venue and selling on the more expensive
one within a single block, capturing the spread risk-free. This is the most widely measured
form of MEV. A BIS report estimated that Ethereum arbitrage MEV exceeded \$200 million in
notional value in 2021 alone.

Arbitrage MEV is considered price-stabilizing - it brings pools to equilibrium faster. Its
negative externality is the Priority Gas Auction (PGA) it triggers: bots bidding up gas fees
to ensure they are first in the block, raising costs for all other network participants.

### Liquidations

Decentralized lending protocols (Aave, Compound, MakerDAO) require borrowers to maintain
collateral above a liquidation threshold. When collateral value drops below the threshold, the
position is available for liquidation: a liquidator can repay the debt and seize the collateral
at a discount, keeping the difference as profit.

Searchers monitor lending protocols continuously for positions approaching their thresholds.
When a liquidation becomes available, multiple bots race to execute it first. The economic
analog is a distressed-asset sale: whoever acts first acquires the collateral at a discount.

The systemic risk is a cascade effect: a large liquidation forces collateral assets onto the
market, suppressing prices, pushing more positions below threshold, triggering further
liquidations. This "volatility-MEV feedback loop" is documented in research by Blocksholes
and TwinStake: volatility creates liquidation MEV, which creates more volatility, which creates
more MEV.

### Front-running

When a large pending swap is visible in the mempool, a searcher can submit a buy order ahead
of it, knowing the large swap will push the price up. The searcher sells immediately after,
capturing the price impact caused by the original trade.

The target trader receives worse execution than expected - they pay more because the
front-runner has already moved the price. This is functionally identical to the broker
front-running practice banned in traditional markets, with the distinction that in DeFi it
operates transparently at the protocol level.

### Back-running

Back-running captures the inverse: a searcher places a transaction immediately *after* a
large swap to exploit the price inefficiency it creates. The most common form is placing an
arbitrage transaction immediately after a large DEX swap that has pushed a pool's price away
from the rest of the market.

Back-running is typically benign for the target trader - it doesn't harm their execution price.
It is a form of automated price correction.

### Sandwich attacks

A sandwich attack combines front-running and back-running against a single target transaction.
The attacker:

1. Detects a large pending swap in the mempool.
2. Submits a buy transaction *before* the target swap, pushing the price up.
3. The target swap executes at the now-elevated price, pushing the price up further.
4. The attacker sells immediately *after*, locking in the profit.

The target trader is the victim: they pay significantly more than the fair market price because
the attacker has deliberately inflated it around their trade. Research on DEX slippage has
found that sandwich attacks push transactions close to the maximum slippage tolerance set
by the routing protocol, extracting the maximum possible value from each target.

Sandwich attacks are the most harmful form of MEV for retail participants. They are also
the most detectable: the pattern (buy, target, sell from the same address within one block) is
visible on-chain.

### Time-bandit attacks

A time-bandit attack is a consensus-level threat. If the MEV available in an *already-confirmed*
block is greater than what can be earned by building on top of the current chain tip, a validator
may attempt to reorganize the chain - discarding recent blocks and replacing them with an
alternative chain that includes the high-value MEV transactions.

This threat is theoretical at scale on Ethereum today, but it is structurally real: whenever
the MEV in a past block exceeds the validator's expected forward revenue, there is an economic
incentive to attempt a reorg. The larger MEV grows as a share of total block revenue, the more
meaningful this risk becomes.

### Oracle front-running

Price oracles (Chainlink, Pyth, protocol-native TWAPs) update asset prices at discrete
intervals. Between an oracle update being submitted to the mempool and its confirmation, a
searcher can see the impending price change and execute trades that profit from it - buying
before a price increase or selling before a decrease.

This is the blockchain equivalent of trading on material non-public information: the oracle
update is the "information event," and the searcher is acting on it before the market has fully
absorbed it.

### Transaction sniping

Transaction sniping is competition between searchers targeting the same MEV opportunity.
When multiple bots detect the same liquidation or arbitrage, they race to include their
transaction first by bidding higher gas fees. This escalates into a Priority Gas Auction that
can consume the majority of the MEV profit in gas costs while raising fees for all unrelated
users transacting in the same block.

## Economic consequences

### Gas fee inflation

PGAs create direct costs for ordinary users. When searchers bid up gas fees to secure block
position, the gas price floor rises for all transactions in that block. During periods of high
MEV activity - volatile markets, large protocol events, liquidation cascades - gas prices can
spike by orders of magnitude above baseline.

The Flash Boys 2.0 paper documented bots incrementally raising gas bids up to 90% of the
available MEV profit, leaving only 10% net after gas costs. For users transacting during the
same period, the cost is a negative externality they bear without any corresponding benefit.

### Volatility amplification

MEV does not only respond to volatility - it amplifies it. The feedback loop runs as follows:

* A price drop pushes lending positions toward liquidation.
* Liquidation bots execute, dumping collateral assets onto the market.
* Selling pressure drives prices down further.
* More positions cross the liquidation threshold.
* The cycle repeats.

Research on Ethereum staking and execution-layer rewards has documented this dynamic,
finding that MEV revenue is highest precisely in the periods when markets are most stressed

* not because MEV is countercyclical, but because stressed markets generate the most
  extractable opportunities.

### Market fairness and adverse selection

Any DeFi protocol whose transaction flow is publicly visible in the mempool faces a structural
adverse selection problem: informed actors (searchers with low-latency bots and private
submission channels) systematically outperform uninformed actors (regular users) not through
better analysis, but through protocol-level access.

This has measurable effects on protocol participation. DEX users who experience repeated
sandwich attacks face worse-than-expected execution outcomes, which is reflected in
higher effective spreads relative to centralized venues. Over time, this degrades DEX
liquidity quality for retail users who cannot access MEV-protected routing.

## Scale

By 2021, Ethereum arbitrage MEV alone exceeded \$200 million in notional value, per BIS
data. Estimates across all MEV types on Ethereum put cumulative extraction in the billions
of dollars since the concept was first measured. The Flashbots transparency dashboard has
tracked hundreds of millions of dollars in MEV-Boost relay payments from builders to
validators since the Merge.

The block building market is highly concentrated: six builders control the majority of Ethereum
block production. The searcher market is similarly concentrated at the top - approximately
20 teams account for the bulk of measurable MEV - but has a long tail of \~500 active
participants deploying 2,800+ bots.

## What this means for data practitioners

MEV is not a theoretical risk. It is a measurable, continuous feature of the Ethereum block
production process. For anyone building on DeFi data:

* **Execution quality analysis** requires accounting for MEV-induced slippage. Observed
  swap prices include the price impact of sandwiching; comparing reported price to VWAP
  without adjusting for MEV structure will overstate execution quality.

* **Liquidation event modeling** must account for the cascade dynamics. Single-block
  liquidation volume is not independent across blocks - it is autocorrelated through the
  volatility-MEV feedback loop.

* **Gas fee time series** are contaminated by PGA activity. Baseline fee estimation during
  high-MEV periods requires separating bot-driven gas spikes from organic demand.

* **Block-level transaction ordering** is not random and not FIFO. The position of a
  transaction within a block is a strategic variable controlled by the block builder, and the
  ordering carries information about which searcher bundles were included.

<div className="my-6 rounded-xl border border-gray-200 dark:border-gray-800 overflow-hidden bg-gray-50 dark:bg-white/[0.02]">
  <div className="px-4 py-2.5 border-b border-gray-200 dark:border-gray-800 flex items-center justify-between">
    <span className="text-xs font-semibold text-gray-500 dark:text-gray-400 uppercase tracking-widest">Dataset Reference</span>

    <a href="https://huggingface.co/BlockDB/datasets" target="_blank" rel="noopener noreferrer" className="inline-flex items-center gap-1.5 text-xs font-semibold rounded-md px-2.5 py-1 transition-opacity hover:opacity-90" style={{ backgroundColor: '#FFD21E', color: '#1a1a1a' }}>
      🤗 Preview free on HF
    </a>
  </div>

  <div className="grid grid-cols-2 sm:grid-cols-4 gap-0 divide-x divide-gray-200 dark:divide-gray-800">
    <div className="px-4 py-3">
      <div className="text-xs text-gray-500 mb-1">Tables</div>
      <div className="text-xs font-mono text-gray-900 dark:text-white leading-relaxed">uniswap\_v4\_swaps<br />uniswap\_v4\_liquidity<br />liquidity\_pools\_reserves</div>
    </div>

    <div className="px-4 py-3">
      <div className="text-xs text-gray-500 mb-1">Chains</div>
      <div className="text-sm text-gray-900 dark:text-white">ETH, Base, Arbitrum<br /><span className="text-xs text-gray-500">+ 8 others</span></div>
    </div>

    <div className="px-4 py-3">
      <div className="text-xs text-gray-500 mb-1">Coverage</div>
      <div className="text-sm text-gray-900 dark:text-white">Block 1 → live</div>
    </div>

    <div className="px-4 py-3">
      <div className="text-xs text-gray-500 mb-1">Delivery</div>
      <div className="text-sm text-gray-900 dark:text-white">WSS · SFTP<br /><span className="text-xs text-gray-500">\<140 ms streaming</span></div>
    </div>
  </div>
</div>

## Glossary

**MEV (Maximal Extractable Value)** - Value extracted by controlling transaction ordering,
inclusion, or exclusion within a block.

**Mempool** - The pool of pending, unconfirmed transactions publicly visible before block
inclusion.

**Searcher** - An entity (typically a bot) that identifies and exploits MEV opportunities.

**Block builder** - A specialized actor that constructs the most profitable block from mempool
transactions and private bundles.

**Proposer-Builder Separation (PBS)** - The architecture separating block construction
(builders) from block proposal (validators).

**Priority Gas Auction (PGA)** - A bidding war between bots raising gas fees to secure
favorable block position.

**Sandwich attack** - An MEV strategy that places transactions before and after a target
trade to profit from the price impact the target causes.

**Liquidation MEV** - Profit extracted by being the first to trigger and settle an
undercollateralized lending position.

<div className="mt-12 p-5 rounded-xl border border-yellow-500/30 dark:border-yellow-500/20 bg-yellow-50/60 dark:bg-gray-800/20 flex flex-col sm:flex-row items-start sm:items-center gap-4">
  <div className="flex-1">
    <p className="text-gray-900 dark:text-white font-semibold">Preview the underlying swap and liquidation data</p>
    <p className="text-gray-600 dark:text-gray-400 text-sm mt-0.5">Explore 1,000+ sample rows from any BlockDB dataset on Hugging Face - no account needed.</p>
  </div>

  <a href="https://huggingface.co/BlockDB/datasets" target="_blank" rel="noopener noreferrer" className="flex-shrink-0 inline-flex items-center gap-2 rounded-lg px-5 py-2.5 text-sm font-semibold transition-opacity hover:opacity-90" style={{ backgroundColor: '#FFD21E', color: '#1a1a1a' }}>
    🤗 Open on Hugging Face
  </a>
</div>

***

Want the full history or production-volume access? [Contact us](https://www.blockdb.io/#contact-us) - production schema, no commitment.

<div className="mt-16 pt-8 border-t border-gray-200 dark:border-gray-800">
  <h3 className="text-lg font-bold text-gray-900 dark:text-white mb-6">You might also like</h3>

  <div className="grid grid-cols-1 sm:grid-cols-2 gap-4">
    <a href="/articles/what-is-mempool-ethereum" className="group relative flex gap-4 items-start p-4 rounded-xl border border-gray-200 dark:border-gray-800 bg-gray-50 dark:bg-white/[0.03] transition-all duration-300">
      <div className="absolute left-0 inset-y-0 w-[3px] rounded-l-xl opacity-0 group-hover:opacity-100 transition-opacity duration-300" style={{ backgroundColor: '#5A86FF' }} />

      <div className="flex-shrink-0 overflow-hidden rounded-lg" style={{ width: '72px', height: '72px' }}>
        <img src="https://mintlify.s3.us-west-1.amazonaws.com/blockdb-24509496/images/posts/what-is-mempool-ethereum.png" alt="What is the mempool" className="w-full h-full object-cover group-hover:scale-105 transition-transform duration-500" />
      </div>

      <div className="flex-1 min-w-0">
        <h4 className="text-sm font-bold text-gray-900 dark:text-white group-hover:text-blue-600 dark:group-hover:text-blue-400 transition-colors leading-snug line-clamp-2">
          What Is the Mempool and How Do MEV Bots Use It?
        </h4>

        <div className="mt-1.5 flex flex-wrap gap-1">
          <span className="text-xs px-1.5 py-0.5 rounded-full bg-gray-100 text-gray-500 dark:bg-white/[0.06] dark:text-gray-400">#Mempool</span>
          <span className="text-xs px-1.5 py-0.5 rounded-full bg-gray-100 text-gray-500 dark:bg-white/[0.06] dark:text-gray-400">#MEV</span>
        </div>

        <span className="mt-1.5 flex items-center gap-1 text-xs text-gray-500">
          Mar 4, 2026 ·

          <svg width="11" height="11" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" aria-hidden="true">
            <circle cx="12" cy="12" r="10" />

            <path d="M12 6v6l4 2" />
          </svg>

          7 min read
        </span>
      </div>
    </a>

    <a href="/articles/glossary" className="group relative flex gap-4 items-start p-4 rounded-xl border border-gray-200 dark:border-gray-800 bg-gray-50 dark:bg-white/[0.03] transition-all duration-300">
      <div className="absolute left-0 inset-y-0 w-[3px] rounded-l-xl opacity-0 group-hover:opacity-100 transition-opacity duration-300" style={{ backgroundColor: '#5A86FF' }} />

      <div className="flex-shrink-0 overflow-hidden rounded-lg" style={{ width: '72px', height: '72px' }}>
        <img src="https://mintcdn.com/blockdb-24509496/9OzcpY8A104W88dS/images/banner.png?fit=max&auto=format&n=9OzcpY8A104W88dS&q=85&s=ff2a9380025aa45e09a033c96b3038d6" alt="DeFi Glossary" className="w-full h-full object-cover group-hover:scale-105 transition-transform duration-500" width="2560" height="1440" data-path="images/banner.png" />
      </div>

      <div className="flex-1 min-w-0">
        <h4 className="text-sm font-bold text-gray-900 dark:text-white group-hover:text-blue-600 dark:group-hover:text-blue-400 transition-colors leading-snug line-clamp-2">
          BlockDB DeFi Data Glossary
        </h4>

        <div className="mt-1.5 flex flex-wrap gap-1">
          <span className="text-xs px-1.5 py-0.5 rounded-full bg-gray-100 text-gray-500 dark:bg-white/[0.06] dark:text-gray-400">#Reference</span>
        </div>

        <span className="mt-1.5 flex items-center gap-1 text-xs text-gray-500">
          Reference ·

          <svg width="11" height="11" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" aria-hidden="true">
            <circle cx="12" cy="12" r="10" />

            <path d="M12 6v6l4 2" />
          </svg>

          5 min read
        </span>
      </div>
    </a>
  </div>
</div>
