Network MEV Timing
Returns network-wide MEV timing-game statistics as a per-day series. Each day carries the slot counts, a timing breakdown, the median slot offset, and the full histogram.
Use case guide: Compare MEV Timing shows how to compare daily network, entity, and validator-set behavior.
Protocol caveat: The 1200 ms and 2600 ms timing bands apply to pre-Glamsterdam slots. Glamsterdam introduces ePBS and restructures slot production, so post-fork classifications may change.
Data provenance: Timing statistics are derived from offchain relay APIs and streams. Relay-reported timestamps, identities, and bid coverage are not independently verifiable from onchain data; coverage gaps or inconsistent reporting can affect results.
Results can be filtered by a time range (bucketed to whole UTC days) and are paginated. Use min_slots_per_day to exclude sparsely-covered days.
Note: MEV relay and timing data is only available on mainnet at this time.
History: Relay bid collection began on 2024-06-03 (UTC). The series contains no days before that date; a time range that falls entirely before it returns an empty result.
Data freshness: the most recent ~3 days of daily aggregates are reprocessed and may still change.
Authorizations
Body
The Ethereum chain to query.
mainnet, hoodi Specify a time range using either Unix timestamps or epoch numbers. If left null, the API will query the entire available history of the selected validators.
- Unix Timestamp
- Epoch
- Slot
Minimum number of slots with relay data a day must have to be included in the results. Filters out sparsely-covered days. Defaults to 100.
x >= 0Cursor value for pagination. See our pagination guide for more details.
The number of items to return per page.
1 <= x <= 10Response
Successful response.
Paginated response containing per-day network-wide MEV timing statistics.
The time span actually covered by the returned results — from the first to the last matching data point — specified in slots, epochs, and Unix timestamps.
This reflects the data that was found, not the range that was queried. When no data is found, it falls back to the requested range, or to the full available history if no range was given.
For arbitrary (custom) time-range queries the queried range is expanded outward to whole UTC days, so the covered range may be wider than requested. As stated above, the reported range still reflects the data that was actually found — a touched UTC day with no data for the selected validators will not extend it.

