Solana slot time cut to 200 ms in four steps

Updated Fact-checked November 10, 2026 4 sources
Short answer

Solana's target slot time, the length of one block slot, went from 400 ms to 200 ms in four 50 ms steps. The features activated on 19 August, 26 August, 16 September and 8 October 2026 (read from their feature accounts), and each took effect one epoch later: the 200 ms step at the start of epoch 1053 on 9 October 2026. For a user, blocks now come twice as often, and a signed transaction left waiting goes stale after about 30 seconds instead of 60.

Read on-chain Protocol upgrades

What changed

A slot is the window in which one validator may produce a block. Solana launched with 400 ms slots. SIMD-0525 cut that in four steps, each behind its own feature gate, and required each step to take effect one epoch after its feature activated. This is one running entry for all four.

Target Feature activated (on-chain, UTC) Took effect (solana.com)
350 ms 2026-08-19 05:50, slot 440,208,000 21 August, epoch 1020
300 ms 2026-08-26 19:29, slot 441,936,000 28 August, epoch 1024
250 ms 2026-09-16 15:03, slot 447,552,000 18 September, epoch 1037
200 ms 2026-10-08 06:28, slot 454,464,000 9 October, epoch 1053

How we read it: each feature account (iBRL5Ru…, iBRLL3k…, iBRLMc8…, iBRLjhJ…; full IDs in Agave’s feature-set source) stores its activation slot; getBlockTime gives the date. A second RPC provider returned the same slots.

What it means if you hold or use SOL

  • Blockhashes expire sooner. A transaction must land within 150 blocks of the blockhash it was signed with. At 200 ms that is about 30 seconds, down from about 60, per solana.com. Signing flows that wait on a person, such as a hardware wallet left on a desk, have less slack.
  • Epochs are shorter. An epoch stays 432,000 slots, so it now lasts about 26 hours, not about two days. That changes when staking rewards arrive and how long unstaking takes; see our entry on epoch length.
  • Inflation is scaled, not cut. SIMD-0525 scales the protocol’s slots-per-year figure with each step, so the network’s rate is now per protocol year of exactly 200 ms slots. Because real slots run slightly slower, supply grows a little less per calendar year than that rate says; see our supply page.
  • Measured, not target: over 30 recent performance samples on 10 November, a slot took 215 ms on average.

The network did not change its leader rotation (four slots per leader) or the number of slots per epoch.

The live number

This story is dated. For today's reading, see Block time and real throughput, measured and How long an epoch lasts now.

More on these topics

How we verify: an entry is published only when the change is read from the Solana network (feature accounts, the rent and inflation settings, block times, through public RPC endpoints), checked against its primary source (solana.com's upgrade pages, read through Internet Archive copies where solana.com blocks automated readers; SIMD files; a program's own docs or terms; the USPTO record), or reported by at least two independent outlets, in which case we say what is unproven. SolPilled is independent and unofficial, and news entries carry no referral links. All changes · Upgrade log · Methodology

Sources

  1. Solana RPC, getMultipleAccounts on the four reduce_slot_time feature accounts, then getBlockTime (read 2026-11-10)
  2. solana.com: Reduced slot times, updated October 2026 (read through an Internet Archive copy of 2026-10-21)
  3. SIMD-0525: Reduce slot times (solana-improvement-documents)
  4. Agave feature-set source: reduce_slot_time_to_350ms ... 200ms feature IDs