💎 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.
Authorizations
Body
The name of the entity to retrieve MEV timing statistics for (e.g. "Lido", "Coinbase"). Matching is case-sensitive; use the exact name as returned by the entities overview endpoint.
The Ethereum chain to query.
mainnet, hoodi Optional sub-entity to scope the statistics. Omit or pass an empty string to get the entity-level aggregate. Matching is case-sensitive; use the exact name as returned by the sub-entities overview endpoint.
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
Cursor 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 MEV timing statistics for the entity.
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.

