Validator proposed blocks
Retrieve beacon chain blocks proposed by one or more validators within a bounded epoch window. By default, the service returns proposals from the last 100 epochs ending at the latest processed epoch. You can page the window by setting the optional epoch query parameter to an upper bound (inclusive).
The response includes per-block consensus metadata (roots, proposer, counts) and execution payload details when available. Execution fields are null for pre-Merge slots or blocks without an execution payload.
Authorizations
Path Parameters
Comma-separated validator indices and/or public keys (maximum 100 items by default). Each identifier must be either a validator index (base-10 integer) or a 48-byte BLS public key as 0x-prefixed hex (96 hex characters after 0x) or without the 0x prefix. Comma-separated list (no spaces) of validator identifiers. Each identifier must be either:
- A validator index as a base-10 integer (for example, 652648)
- A BLS public key as a 96-hex-character string with or without the 0x prefix (case-insensitive)
Resolution and limits:
- The server resolves public keys to validator indices before querying data.
- The total number of identifiers must not exceed the server-enforced limit (default 100).
- Identifiers that cannot be parsed or resolved result in HTTP 400.
"1,2,3"
Query Parameters
Upper bound for the epoch window (inclusive). Results include proposals from epochs in the range [epoch-100, epoch]. Defaults to the latest processed epoch when omitted. Must be a non-negative integer.
x >= 0399359
Response
Matching proposals were retrieved successfully. The data array contains one item per block proposed by any of the specified validators within the requested epoch window.

