A slot in which the assigned leader validator fails to produce a block, resulting in no entries being added to the ledger for that slot. Slots are skipped when the leader is offline, too slow to produce a block within the time window, or unable to reach other validators. Skipped slots do not increment block height and contribute to a validator's skip rate metric.
Start with the shortest useful explanation before going deeper.
A slot in which the assigned leader validator fails to produce a block, resulting in no entries being added to the ledger for that slot. Slots are skipped when the leader is offline, too slow to produce a block within the time window, or unable to reach other validators. Skipped slots do not increment block height and contribute to a validator's skip rate metric.
Use the quick analogy first so the term is easier to reason about when you meet it in code, docs, or prompts.
Think of it as a building block that connects one definition to the larger Solana system around it.
Place the term inside its Solana layer so the definition is easier to reason about.
Clusters, nodes, MEV actors, routing, and operating environments.
Turn the term from vocabulary into something operational for product and engineering work.
This term unlocks adjacent concepts quickly, so it works best when you treat it as a junction instead of an isolated definition.
Use this compact block when you want to give an agent or assistant grounded context without dumping the entire page.
Skipped Slot (skipped-slot) Category: Network Definition: A slot in which the assigned leader validator fails to produce a block, resulting in no entries being added to the ledger for that slot. Slots are skipped when the leader is offline, too slow to produce a block within the time window, or unable to reach other validators. Skipped slots do not increment block height and contribute to a validator's skip rate metric. Related: Slot, Skip Rate, Leader Schedule
Use glossary context, relationships, mental models, and builder paths to get structured answers instead of generic chat output.
Optional: paste Anchor, Solana, or Rust code so the Copilot can map primitives back to glossary terms.
The Copilot will answer using the current term, related concepts, mental models, and the surrounding glossary graph.
These branches show which concepts this term touches directly and what sits one layer beyond them.
A time window during which a designated leader validator can produce a block. Each slot lasts approximately 400 milliseconds. Slots are numbered sequentially from genesis and grouped into epochs of 432,000 slots (~2-3 days). Not every slot produces a block—a skipped slot means the leader was offline or too slow.
The percentage of assigned leader slots in which a validator fails to produce a block, either due to being offline, misconfigured, behind on the fork, or unable to process transactions fast enough. A high skip rate indicates validator unreliability; it reduces staking rewards for both the validator and its delegators because skipped slots produce no block rewards. Solana publishes per-validator skip rates via the `getVoteAccounts` RPC method, and delegators use skip rate as a key signal when selecting validators.
A deterministic mapping of slots to validators for an entire epoch, computed from stake weights. Validators with more stake are assigned proportionally more leader slots. The schedule is derived using a seed from the previous epoch's randomness, so all validators independently compute the same schedule without coordination.
These are the next concepts worth opening if you want this term to make more sense inside a real Solana workflow.
Glossary entries become useful when they are connected. These links are the shortest path to adjacent ideas.
A time window during which a designated leader validator can produce a block. Each slot lasts approximately 400 milliseconds. Slots are numbered sequentially from genesis and grouped into epochs of 432,000 slots (~2-3 days). Not every slot produces a block—a skipped slot means the leader was offline or too slow.
The percentage of assigned leader slots in which a validator fails to produce a block, either due to being offline, misconfigured, behind on the fork, or unable to process transactions fast enough. A high skip rate indicates validator unreliability; it reduces staking rewards for both the validator and its delegators because skipped slots produce no block rewards. Solana publishes per-validator skip rates via the `getVoteAccounts` RPC method, and delegators use skip rate as a key signal when selecting validators.
A deterministic mapping of slots to validators for an entire epoch, computed from stake weights. Validators with more stake are assigned proportionally more leader slots. The schedule is derived using a seed from the previous epoch's randomness, so all validators independently compute the same schedule without coordination.
These entries live beside the current term and help the page feel like part of a larger knowledge graph instead of a dead end.
Solana's primary production cluster where real SOL and real economic activity occur; the "beta" designation reflects the network's ongoing protocol development despite being fully live since March 2020. It uses the same architecture as other clusters but with real validator stakes, live staking rewards, and permanent on-chain state. All production dApps, tokens, and NFTs exist on Mainnet Beta.
A persistent public Solana cluster intended for application development and testing, running the same software version as Mainnet Beta but with no real economic value. Devnet SOL can be freely airdropped via the CLI or faucet APIs, and the ledger may be reset periodically by Solana Labs. Developers use Devnet to test programs and integrations before deploying to Mainnet Beta.
A public Solana cluster used primarily by the Solana core team and validators to test new software releases, performance benchmarks, and network upgrades under real network conditions before they reach Mainnet Beta. Testnet SOL has no monetary value, and the ledger is reset more frequently than Devnet; it is less suitable for application development and more suited for validator operators validating their infrastructure.
The rate at which a Solana cluster processes and commits transactions; Solana's theoretical maximum exceeds 65,000 TPS due to its parallel execution model, though real-world sustained throughput on Mainnet Beta typically ranges from 2,000–5,000 non-vote TPS under normal load. Vote transactions (used for consensus) make up a significant portion of all on-chain activity and are counted separately. High TPS is enabled by Proof of History timestamps, Sealevel parallel execution, and Gulf Stream mempool-less forwarding.