MEV Timing

Returns the MEV timing-game outcome for a single block: the winning relay bid, the earliest later bid that would have beaten it (first_better_bid), the highest-value later bid (best_later_bid), the value left on the table, and the winning relay and builder.

Use case guide: Investigate a Block shows how to interpret the winning bid, later alternatives, and missed value.

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 and bid fields are derived from offchain relay APIs and streams. Relay-reported timestamps, identities, and bid coverage are not independently verifiable from onchain data; verify included block fields separately.

Resolve a block by number or the keywords "latest" / "finalized". Pair this with /api/v2/ethereum/validators/proposal-slots to drill into a specific proposal.

Note: MEV relay and timing data is only available on mainnet at this time.

History: Relay bid collection began on 2024-06-03 (UTC). Blocks before that date — including all pre-Merge blocks — return status unknown, since the absence of relay data means the timing outcome is not known rather than that no MEV occurred.

Data freshness: per-slot relay statistics lag the chain head by roughly 4 hours. A block newer than the latest aggregated slot returns status pending until the data catches up.

{
  "data": {
    "status": "timing_games",
    "first_better_bid": {
      "status": "timing_games"
    },
    "best_later_bid": {
      "status": "timing_games"
    }
  }
}