๐ Builder Performance Aggregate
Returns the delivery and settlement record of the selected builders over an evaluation window: the proposals whose accepted bid they won, what happened to the execution payloads, whether the chain paid the bid values, and how much of the promised trusted payments the payloads delivered. The figures are raw counts and amounts, not a score.
From the Glamsterdam hard fork on, a proposer accepts a builderโs bid and the builder reveals the execution payload later. The bid value is paid from the builderโs balance when the chain includes the payload, and also when same-slot attester weight reached the builder-payment quorum although the chain did not include it. A trusted payment is an amount the builder promises to transfer inside the payload; the chain never checks or enforces it.
Only finalized slots whose execution payload status is decided count, and the window never reaches before the fork. The window ends at the last such slot, at most the last slot of the epoch before the head; range returns the window evaluated, or the requested window when no slot of it is decided yet. A builder that won nothing in the window returns zero counts. Bid values and payments are stored in Gwei and returned in wei.
Combine this endpoint with others for deeper insights:
- The proposals behind these figures, one row each: v2/ethereum/builders/proposal-slots with the same
builderselector - The registry entries of the builders, with balances and status: v2/ethereum/builders
- The market share of every curated builder entity: v2/ethereum/builders/entities
Premium Endpoint: This endpoint requires a Scale or Enterprise plan.
Authorizations
Body
Select builders by one of these options. Every endpoint that uses this selector requires a Scale or Enterprise plan:
- builder_pubkey: One builder, by its public key, as in
execution_payload.builder_pubkey. The best way to follow one builder over time. - builder_index: The builder that holds this index now. To select the builder of a past slot, use that slot's
builder_pubkey. - builder_execution_address: Every builder that withdraws to this execution layer address. Use it for all the builders of one operator.
- builder_entity: Every builder that withdraws to an address that beaconcha.in curated under this name. Optionally include
builder_sub_entity. Matching is case-sensitive.
Note: When a builder exits and withdraws its whole balance, the chain gives its index to the next new builder, so one index can name different builders over time. Every option therefore resolves to builder public keys, and a proposal counts for a builder only from the epoch it took the index until the epoch the next builder took it. The builder registry exists from the Glamsterdam hard fork on. An option that matches no builder returns 404. A builder that matches but has nothing in the result returns an empty list or zero counts, not 404.
- Builder Public Key
- Builder Index
- ๐ Builder Execution Address
- ๐ Builder Entity
The Ethereum chain to query.
mainnet, hoodi Response
Successful response.
Response containing the delivery and settlement record of the selected builders over the evaluation window.
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.

