# Ethereum slots and missed blocks: why a slot can have no block Ethereum proof of stake divides time into slots, currently 12 seconds each, grouped into 32-slot epochs. A slot is an opportunity for an assigned proposer to produce a block; it is not a guarantee that a block appears. Missed slots therefore make block count and elapsed time differ. The slot schedule and finality are also different concepts. Evidence: [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/) Canonical: https://degreesofsatoshi.com/encyclopedia/ethereum-slots-and-missed-blocks/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Slot:** The documented mainnet slot duration is 12 seconds. ([Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/)) - **Epoch:** An epoch contains 32 slots. ([Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/)) - **Opportunity:** A selected proposer is assigned to each slot. ([Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/)) ## Time keeps moving when a proposer misses Consensus duties are assigned against the slot and epoch schedule. A proposer can fail to produce a usable block, but the clock still advances to the next slot. Later blocks can build on the earlier available chain. This is why a slot number is not the same as an execution block number. A block explorer can show gaps in consensus slots without implying that every gap contains a hidden transaction block. Evidence: [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/) ## Count time separately from blocks Under the documented schedule, five slot intervals represent 5 × 12 = 60 seconds. If one scheduled slot in that span is missed, there are fewer produced blocks than scheduled opportunities. The exact count also depends on how you choose the endpoints of the interval. An epoch lasts 32 × 12 = 384 seconds, or 6 minutes 24 seconds, under this schedule. That arithmetic does not say a transaction is finalized after exactly one epoch. Evidence: [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/) ## A schedule is not a settlement guarantee Transaction inclusion depends on a proposer including the transaction in a valid block. Finality requires the consensus voting conditions, which can be delayed by network problems. Neither is guaranteed merely because a certain number of seconds passed. For a payment, inspect the actual included block and its confirmation or finality status. Use slot timing to understand the schedule, not as a substitute for those observations. Evidence: [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/) ## Questions ### Does Ethereum produce a block every 12 seconds without exception? No. Twelve seconds is the documented slot interval. A slot can be missed, so an actual block is not guaranteed for every opportunity. Evidence: [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/) ### Are 32 slots always 32 produced blocks? No. An epoch has 32 scheduled slots, but missed proposals can make the number of produced blocks smaller. Evidence: [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/); [The Merge](https://ethereum.org/en/roadmap/merge/) ## Claims and scope ### ethereum-slots-and-missed-blocks-quick-answer Ethereum proof of stake divides time into slots, currently 12 seconds each, grouped into 32-slot epochs. A slot is an opportunity for an assigned proposer to produce a block; it is not a guarantee that a block appears. Missed slots therefore make block count and elapsed time differ. The slot schedule and finality are also different concepts. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-slots-and-missed-blocks-fact-slot Slot: The documented mainnet slot duration is 12 seconds. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-slots-and-missed-blocks-fact-epoch Epoch: An epoch contains 32 slots. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### ethereum-slots-and-missed-blocks-fact-opportunity Opportunity: A selected proposer is assigned to each slot. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Ethereum proof of stake](https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/) — ethereum.org contributors. Consensus proposal schedule, voting and finality distinctions. Locator: Slots; epochs; block proposals; attestations; finality. Retrieved: 2026-10-02T18:55:26.560Z. - [The Merge](https://ethereum.org/en/roadmap/merge/) — ethereum.org contributors. Consensus transition preserved execution balances and transaction history. Locator: Merging with Mainnet; misconceptions. Retrieved: 2026-10-02T18:55:26.611Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Ethereum slots and missed blocks: why a slot can have no block.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-slots-and-missed-blocks/