Relayer landscape
In this page we track the most important statistics relating to the operation of MEV Relays introduced with the advent of mev-boost in PoS Ethereum.
Total value relayed
The total value paid to validators in order to facilitate the production of blocks crafted by block builders. This is a combination of priority_fees
and baseline_mev
. This should be equal to the value of the sum of winning_bid
observed accross relays.
Active relays
The number of active relays that facilitate block production in Ethereum Mainnet at present. You will find links to those relay endpoints below.
Value over vanilla blocks
The value surplus that blocks that were procured from MEV Relays exhibit, when compared to the locally built (vanilla) blocks. This is a comparison of aggregate average values, over the time-span of the toggled time period, and is derived from the execution layer rewards that these blocks pack for validators.
MEV facilitated
This is an estimation of the gross amount of MEV that the relays have facilitated over time. It is based on a sum
of our Baseline MEV computation across the period in question.
mev-boost ✗ vs mev-boost ✔
An aggregate comparison between blocks that have been produced locally (mev-boost ✗) and blocks that have been procured from MEV relays (mev-boost ✔)
Sample size
The size of the sample of blocks in the RatedDB, that relate to the time period toggled.
Average transactions included
The number of transactions that either category of blocks packed in the respective time-period, on average.
Average execution rewards
The value of the execution layer rewards for validators that the average block in either category packed over the time period toggled. Learn more about how we go about computing those in Baseline MEV computation.
Average consensus rewards
The value of the cosensus layer rewards that the average block in either category packed over the time period toggled.
Average total rewards
The sum of execution and consensus layer rewards for either category of blocks.
Relay market share
Due to the lack of data from relays around the submission of validator signatures when proposers source MEV-boost blocks, there has been no clear way to attribute a MEV-boost block to a single relay when said block appears on more than one relay.
As a stop-gap measure, we are attributing a +1
counter to every relay that revealed the winning bid to the block proposer. This obviously leads to poor accounting as the sum of bids revelead will be greated than the sum of blocks produced. To counter this, we are only adopting this approach on comparative screens and do not account for it in other sums.
Last updated