> ## Documentation Index
> Fetch the complete documentation index at: https://docs.beaconcha.in/llms.txt
> Use this file to discover all available pages before exploring further.
# Introduction
> Analyze MEV timing behavior across the Ethereum network, entities, validator sets, and individual blocks
## Overview
The MEV Timing APIs let you measure when winning relay bids arrive relative to the start of an Ethereum slot. Use them to track network trends, compare staking operators, profile your validators, or audit the bid ladder behind a single proposal.
**API Endpoints:** This section covers the five MEV timing endpoints:
| Endpoint | Best For |
| ------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
| [`/api/v2/ethereum/mev-timing`](/api-reference/ethereum/mev-timing) | Daily network-wide timing trends |
| [`/api/v2/ethereum/entity/mev-timing`](/api-reference/ethereum/entity/mev-timing) | Daily entity or sub-entity trends |
| [`/api/v2/ethereum/validators/mev-timing-aggregate`](/api-reference/ethereum/validators/mev-timing-aggregate) | A 180-day timing profile for a validator set |
| [`/api/v2/ethereum/block/mev-timing`](/api-reference/ethereum/block/mev-timing) | The winning and later-bid outcome for one block |
| [`/api/v2/ethereum/block/mev-bids`](/api-reference/ethereum/block/mev-bids) | The complete relay bid ladder for one block |
MEV relay and timing data is currently available on **mainnet only**. Relay bid collection began on **June 3, 2024 (UTC)**, so earlier periods do not have timing history.
***
## Guides in This Section
Compare daily network and entity behavior, then profile a validator set over the rolling 180-day window.
Inspect the winning bid, value left on the table, and the full relay bid ladder for one proposal.
***
## Interpret MEV Timing Data
API references: [Network timing](/api-reference/ethereum/mev-timing) and [block timing](/api-reference/ethereum/block/mev-timing).
When comparing results, use the same protocol era and report relay coverage alongside the timing outcome. The current classification thresholds describe pre-Glamsterdam slots; post-fork classifications may change as slot production changes.
Read [MEV Timing Games](/mev-timing-games/introduction) for the slot clock, why the 1.2-second and 2.6-second thresholds matter, and how delay affects attesters.
***
## Choosing the Right Endpoint
| Question | Endpoint | Result Shape |
| --------------------------------------------------- | --------------------------------- | ------------------------------------------------------------------------- |
| Is timing-game activity increasing across Ethereum? | `ethereum/mev-timing` | Paginated UTC daily series |
| Is an operator's behavior changing over time? | `ethereum/entity/mev-timing` | Paginated UTC daily series for an entity or sub-entity |
| What is the overall posture of my validators? | `validators/mev-timing-aggregate` | One timing label and a 22-bucket histogram for 180 days |
| What happened in this proposal? | `block/mev-timing` | Winning bid, later alternatives, missed value, relay count, and bid count |
| Which relay bids arrived, and when? | `block/mev-bids` | Paginated bid ladder ordered by arrival time |
The entity daily series and full block bid ladder require a Scale or Enterprise plan. The validator aggregate accepts validator identifiers and dashboard selectors on free plans; address and entity selectors require Scale or Enterprise.
***
## Quick Start: Network Timing Trend
Fetch a daily network series for June 2026. Timestamp ranges are inclusive and the endpoint buckets them into whole UTC days.
```bash theme={null}
curl --request POST \
--url https://beaconcha.in/api/v2/ethereum/mev-timing \
--header 'Authorization: Bearer ' \
--header 'Content-Type: application/json' \
--data '
{
"chain": "mainnet",
"range": {
"timestamp": {
"start": 1780272000,
"end": 1782863999
}
},
"min_slots_per_day": 100,
"page_size": 100
}
'
```
Each row contains exact category counts and a 22-bucket histogram. The illustrative response below shortens the histogram to two buckets:
```json theme={null}
{
"data": [
{
"timestamp": 1780272000,
"date": "2026-06-01",
"slots_with_relay": 6812,
"slots_with_relay_winners": 6475,
"slots_without_relay": 388,
"timing_breakdown": {
"on_time_mev": 5118,
"timing_games": 1214,
"aggressive_tg": 143
},
"median_slot_offset_ms": 984,
"histogram": [
{
"slot_offset_ms_min": -200,
"slot_offset_ms_max": 0,
"count": 12,
"max_value": "84000000000000000"
},
{
"slot_offset_ms_min": 0,
"slot_offset_ms_max": 200,
"count": 146,
"max_value": "132000000000000000"
}
]
}
],
"paging": {
"next_cursor": ""
},
"range": {
"slot": { "start": 14453998, "end": 14669998 },
"epoch": { "start": 451687, "end": 458437 },
"timestamp": { "start": 1780272000, "end": 1782863999 }
}
}
```
For a daily row, the timing-game share among identified relay winners is:
```text theme={null}
(timing_games + aggressive_tg) / slots_with_relay_winners
```
Use `slots_with_relay_winners` as the denominator when analyzing timing behavior. `slots_with_relay` and `slots_without_relay` measure relay-data coverage, not timing categories, and should not be added to `timing_breakdown`.
***
## Reporting Guidance
For finalized reporting, exclude the newest three daily buckets. For a recent block, retry provisional results instead of treating them as evidence that no MEV occurred. The exact freshness and readiness behavior is documented on each linked API reference.
Convert wei with integer or decimal arithmetic: `1 ETH = 10^18 wei`. Avoid binary floating-point for financial totals.
***
## Related Resources
* [Compare MEV Timing](/use-cases/compare-mev-timing) — Benchmark entities and validator sets against the network
* [Investigate a Block](/use-cases/investigate-mev-block) — Audit one proposal and its relay bid ladder
* [MEV Timing Games](/mev-timing-games/introduction) — Conceptual explanation of timing games and their risks
* [API Pagination](/api/pagination) — Follow cursors for daily series and bid ladders