๐ MEV Timing per Day
Returns the MEV timing-game statistics of a set of validators as a per-day series. The validator set may be selected by identifiers, dashboard or dashboard group, withdrawal credential or address, deposit address, or the entities that own or run them (entities). Each day covers the slots in which one of the validators proposed a block that came from a relay.
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 only. Glamsterdam introduces ePBS, and from its Gloas fork epoch on the arrival time of the winning relay bid no longer measures proposer timing. The series therefore ends at the fork: the fork day covers only its pre-fork slots, and later days are absent.
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.
Validator set: The selector is evaluated when you call the endpoint, and every day of the series counts the blocks of the validators it matches at that time. Dashboard, address and entities selectors therefore apply their current members to past days. A selector that matches no validator returns 404. A day on which none of the validators proposed a block that came from a relay is absent from the series.
Results can be filtered by a time range (bucketed to whole UTC days) and are paginated, newest day first. For one histogram of the same validators over a fixed evaluation window, use v2/ethereum/validators/mev-timing-aggregate. For the whole network over the same days, use v2/ethereum/mev-timing.
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: a day appears about 4 to 5 hours after it ends, once the relay data of all its slots is aggregated; the current day is never included. Rows change only when relay data is reprocessed.
Premium Endpoint: This endpoint requires a Scale or Enterprise plan.
Authorizations
Authorization header with value: Bearer YOUR_TOKEN. Refer to the API Keys section to create your API key.
Body
Free selectors available to all users:
- validator_identifiers: One or more validator indices or public keys to filter by.
- dashboard_id: Your beaconcha.in dashboard ID (requires a free account).
Premium selectors for Scale & Enterprise plans (https://beaconcha.in/pricing):
- withdrawal: The validator's withdrawal credential or the Ethereum wallet address used for withdrawals.
- deposit_address: The Ethereum wallet address used for the validator's deposit.
- entity: The name of the assigned entity (e.g., "Lido", "Coinbase"). Optionally include
sub_entityfor more specific filtering. Matching is case-sensitive. Deprecated: useentitiesinstead; Migrating to Owners and Operators gives the sunset date. - entities: The entity that owns the validators (
owner), the one that runs them (operator), or both, each byidorpath.
Note: The set of validators matched by deposit_address and withdrawal selectors is updated once per epoch (~6.4 minutes). Newly deposited validators may take up to one epoch to appear in query results.
Note: The set of validators matched by entity selector is updated once per day.
Note: The set of validators matched by entities is refreshed hourly; a newly deposited validator, or one whose owner or operator changed, can take up to an hour to be matched.
- Indices/Pubkeys
- Dashboard
- ๐ Deposit
- ๐ Withdrawal
- ๐ Entity (deprecated)
- ๐ Owner / Operator
Cursor value for pagination. See our pagination guide for more details.
Response
Successful response.
Paginated response containing per-day MEV timing statistics for the selected validators.
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 the response is 200 but no data is found, it falls back to the requested range, or to the full available history if no range was given. Some endpoints answer 404 instead when no data is found.
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.

