How Ethereum Block Production Works: Slots and Epochs Explained

Ethereum produces blocks on a fixed schedule: time is divided into 12-second slots, grouped into epochs of 32 slots (about 6.4 minutes each), and in every slot the network's proof-of-stake protocol pseudo-randomly assigns one active validator the right to propose a block, while a separate committee of other validators is assigned to attest to it.

The slot: Ethereum's basic heartbeat

Every 12 seconds, a new slot begins. Ahead of time — using a source of on-chain randomness called RANDAO, combined with each validator's stake — the protocol has already determined which single validator, from the entire active validator set, has the right to propose a block for that slot. That validator assembles a block from pending transactions (drawing from the mempool), broadcasts it to the network, and other validators check it and attest.

Not every slot produces a block. If the assigned proposer is offline, misses the window, or the block doesn't propagate in time, the slot is simply skipped, and the chain moves on to the next slot's proposer. This is normal and doesn't harm the network — it just means that block height and slot number aren't always identical, since some slots contribute no block at all.

The epoch: where validator duties are organized

An epoch groups 32 consecutive slots together and is the unit the protocol uses to organize larger-scale validator responsibilities:

• Committee assignment. At the start of each epoch, the full active validator set is shuffled and divided into committees, with each committee assigned to a specific slot within that epoch to submit attestations.
• Attestations. Every validator, once per epoch, submits an attestation — a vote on what it considers the current head of the chain (informing the fork choice rule) and on Casper FFG checkpoint justification (informing finality).
• Rewards and penalties. Validators earn rewards for timely, correct attestations and block proposals, and face small penalties for being offline or slow, with much larger penalties (slashing) reserved for provable protocol violations like double-signing.

Unit	Duration	What happens
Slot	12 seconds	One validator may propose a block; a subset of validators attest
Epoch	32 slots (~6.4 minutes)	Validator committees are reshuffled; attestations accumulate toward justification/finality
Finalization	2 epochs (12–15 minutes)	Checkpoints become cryptoeconomically irreversible

How a proposer is chosen

Validator selection uses RANDAO, a mechanism where each block proposer contributes a piece of randomness (via their signature) that mixes into a seed used to determine future proposer and committee assignments. No single validator can fully predict or control the outcome, since the final randomness depends on contributions accumulated across many prior blocks — though a proposer can, in a limited way, choose whether to reveal their contribution, a well-known and studied nuance called "RANDAO biasing" that has a bounded, small impact rather than letting anyone pick outcomes freely.

What happens inside a slot, step by step

1. The assigned proposer builds a block, selecting transactions from the mempool (often via a separate block-building market rather than picking manually), and includes attestations gathered from prior slots.
2. The proposer signs and broadcasts the block to the peer-to-peer network.
3. The committee assigned to that slot verifies the block against consensus rules and broadcasts their attestations.
4. Other nodes apply the fork choice rule to determine the current canonical chain tip based on accumulated attestation weight.
5. Over subsequent epochs, enough consistent attestation accumulates to justify, and eventually finalize, the checkpoint containing this block.

Why the fixed schedule matters

Having a strict, predictable slot and epoch schedule — rather than a variable block time like Bitcoin's roughly-10-minute average — gives Ethereum predictable timing for reward calculations, validator committee rotation, and the finality process. It also makes network-wide coordination simpler: every node, everywhere, can independently calculate which validator should be proposing right now and which committee should be attesting, without needing to ask anyone.

Missed slots and network health

Empty slots aren't just a theoretical edge case — they happen regularly across the network, for reasons ranging from a proposer's node being temporarily offline to network-wide latency spikes affecting propagation. Client teams and researchers track the empty-slot rate as a rough health indicator: a network running smoothly sees the overwhelming majority of slots filled, while a rising rate of missed slots can point to broader connectivity issues, client bugs, or unusual validator behavior worth investigating. This is one reason Ethereum's community places real emphasis on client diversity — running a mix of different validator and execution client software across the network — since a bug in one dominant client could otherwise cause a correlated wave of missed slots across a large share of validators simultaneously.

Block building versus block proposing

In today's Ethereum, the simple picture of "the assigned proposer picks transactions from the mempool" is often a step removed from what actually happens. A separate, competitive market of specialized block builders assembles fully-formed blocks — bundling transactions in whatever order maximizes total value, including MEV opportunities — and submits these completed blocks to proposers through a relay. The assigned proposer typically just picks the most valuable block offered rather than constructing one from scratch. This separation, often called proposer-builder separation, is intended to reduce the advantage a proposer would otherwise have from being able to see and act on pending transactions directly, and it's an active area of ongoing protocol research rather than a finished, final design.

Bottom line

Ethereum's block production runs on a strict rhythm: a new slot every 12 seconds, with one validator given the right to propose a block and a rotating committee assigned to attest, all organized into 32-slot epochs that structure the path toward finality. This predictable cadence is what makes the rest of Ethereum's consensus mechanics — proposer selection, attestation accounting, and eventual finalization — function as a coordinated, network-wide process rather than an ad hoc race.