๐ Builder Network Performance
Returns the delivery and settlement record of all external builders together over an evaluation window, next to the proposals whose proposer built the execution payload itself. The top-level fields cover the proposals won by external builders and have the same names and meanings as on v2/ethereum/builders/performance-aggregate, so the record of chosen builders compares field by field with the networkโs. Self-built proposals count only in blocks and self_built, never in blocks_won, payload, settlement or trusted_payment. 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, and trusted_payment.delivered counts only the payloads checked so far (see trusted_payment.unchecked_count).
Only finalized slots whose execution payload status is decided count, and the window never reaches before the fork. A missed slot has no proposal and does not count. 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 with zero counts when no slot of it is decided yet. Bid values and payments are stored in Gwei and returned in wei.
Combine this endpoint with others for deeper insights:
- The same figures for chosen builders: v2/ethereum/builders/performance-aggregate
- The market share of every curated builder entity: v2/ethereum/builders/entities
- The proposals of chosen builders, one row each: v2/ethereum/builders/proposal-slots
- The builder registry, with balances and status: v2/ethereum/builders
Premium Endpoint: This endpoint requires a Scale or Enterprise plan.
Authorizations
Body
Response
Successful response.
Response containing the delivery and settlement record of all external builders over the evaluation window, next to the self-built proposals.
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.

