v1

latestOpenAPI 3.0.42026-07-2233241175.9 KB
Network

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.

post/api/v2/ethereum/mev-timing

Request body

chain'mainnet' | 'hoodi'

The Ethereum chain to query.

min_slots_per_dayinteger

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.

cursorstring

Cursor value for pagination. See our pagination guide for more details.

page_sizeinteger

The number of items to return per page.

Response

Successful response.