Skip to main content
POST
💎 MEV Timing

Authorizations

Authorization
string
header
required

Authorization header with value: Bearer YOUR_TOKEN. Refer to the API Keys section to create your API key.

Body

application/json
entity
string
required

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.

chain
enum<string>
default:mainnet

The Ethereum chain to query.

Available options:
mainnet,
hoodi
sub_entity
string

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.

range
Unix Timestamp · object

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.

cursor
string
default:""

Cursor value for pagination. See our pagination guide for more details.

page_size
integer
default:10

The number of items to return per page.

Required range: 1 <= x <= 10

Response

Successful response.

Paginated response containing per-day MEV timing statistics for the entity.

data
object[]
required
range
object
required

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.

paging
object