💎 MEV Timing

Returns an entity's MEV timing-game statistics as a per-day series. Optionally scope to a sub-entity; omit sub_entity for the entity-level rows.

Use case guide: Compare MEV Timing shows how to benchmark an entity or sub-entity against the network.

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. For an aggregated posture and histogram over an entity (rather than a daily series), use /api/v2/ethereum/validators/mev-timing-aggregate with its entity selector.

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.

Premium Endpoint: This endpoint requires a Scale or Enterprise plan.