Epoch
Returns a rolled-up overview of a single consensus layer epoch.
In Ethereum, an epoch is a fixed window of consensus layer slots (32 on Ethereum Mainnet) over which validator attestations are aggregated and finality is determined. This endpoint summarizes network-wide activity for the epoch: validator participation, balances, block proposal outcomes, and the protocol events (deposits, withdrawals, exits, slashings) included across its slots.
Think of it as a per-epoch starting point: the slots range tells you which slots belong to the epoch so you can drill into per-slot detail via v2/ethereum/slot, and the counts point you to the more specific endpoints for each topic.
You can query by epoch number, or use “latest” / “finalized” for the most recent or finalized epoch. The “finalized” view can lag the chain’s latest finalized epoch by up to one epoch so that every metric of the returned epoch is fully populated.
Note: for an epoch whose duties have not yet been fully aggregated (the most recent epochs, whether not-yet-finalized or queried by number just after finalization) the participation- and performance-based fields (attesting_balance, participation_rate, attestation_participation, sync_participation, beaconscore) are null — check finality to tell an in-progress epoch apart, and query “finalized” for a complete, stable response.
Authorizations
Body
Response
Successful response.
Response containing basic information about the epoch.
Rolled-up overview of a single consensus layer epoch.
An epoch spans a fixed window of consensus layer slots (32 on Ethereum Mainnet) during which validator duties are scheduled and attestations are aggregated. This endpoint summarizes network-wide activity for the epoch and provides the slot range you can use to drill into individual slots via the slot endpoints.

