Home » Blockchain » Solana Reaches 200ms Slots in Final SIMD-0525 Step

Solana Reaches 200ms Slots in Final SIMD-0525 Step

Solana’s target slot time reached 200ms on October 9, 2026, the fourth and last cut in SIMD-0525. Earlier steps ran 15 to 19ms above target, and finality is still a…

Abstract blue light trails depicting the speed of the Solana 200ms upgrade

On Friday, October 9, 2026, Solana’s target slot time dropped to 200 milliseconds at epoch 1053. Anza confirmed the change at 14:42 UTC, per Solana Compass. It was the fourth and last cut in SIMD-0525, which began on August 21 at 400 milliseconds. A slot is the interval in which one validator may produce a block. Solana can skip slots, so the slot rate is a target, not a guaranteed block rate.

What’s new

  • The slot target is now 200 milliseconds, half of the 400 milliseconds the network started from.
  • A recent blockhash expires after about 30 seconds, down from 60.
  • A validator’s leader window is 800 milliseconds, down from 1.6 seconds.

What stays the same or isn’t confirmed

  • Total capacity per second is meant to stay roughly constant. The Block reports the proposal does not aim to raise throughput.
  • Full finality still takes about 12.8 seconds.
  • No measured average slot time exists yet for 200 milliseconds.
  • Alpenglow, which targets about 150 milliseconds, has no mainnet date.

Four steps down from 400

The cuts came one at a time. Each stage activated separately and could pause if too many validators missed their slots. Block skip rate was the gating criterion for each step, per Solana Compass, which is also the source for the table. The Block covered the first cut in August.

Target Mainnet date Epoch Measured average slot
350 ms Aug 21, 2026 1020 365 to 367 ms
300 ms Aug 28, 2026 1024 315 to 317 ms
250 ms Sep 18, 2026 1037 266 to 269 ms
200 ms Oct 9, 2026 1053 Not yet measured

What this means for apps and validators

Per-slot limits scale with slot time, so each block has about half the room it had at 400 milliseconds. Solana Compass lists these effects for developers. Signing flows that wait for a person to approve a payment have less time before the blockhash expires. Code should read slot duration from the network or use getBlockTime instead of hardcoding 400 milliseconds.

A KuCoin analysis adds that shorter slots double vote traffic and give marginal hardware less time per slot. KuCoin’s blog is promotional and its claims are not independently verified.

Where the numbers stop

200 milliseconds is the protocol target. Solana Compass had no measured average yet because epoch 1053 had run under an hour when it published. Earlier epochs overshot their targets by 15 to 19 milliseconds each. If that holds, real slots may average around 215 to 220 milliseconds, but that is our extrapolation, not a measurement.

An epoch is 432,000 slots, so it is about 24 hours nominally at 200 milliseconds. Compass estimates roughly 26 hours if the overshoot persists. At 400 milliseconds an epoch was 48 hours nominal. We found no source measuring trader slippage or oracle accuracy gains, and claims about dollar savings on swaps are unsupported.

Who Benefits and How

  • Developers get shorter block intervals to build against, and a clear list of assumptions to check.
  • Validator operators take on tighter timing, and marginal hardware has less room per slot.
  • Ordinary users will mostly see no direct change yet. The change is live on mainnet, but no source measures gains in swap costs or oracle accuracy, and finality is still about 12.8 seconds. Faster finality would have to come from Alpenglow, which has no mainnet date.

Quick answers

Does 200ms mean transactions are final in 200ms? No. Finality is separate and currently takes about 12.8 seconds, per The Block and Solana Compass.

Is Solana now processing twice the transactions? No source we opened says so. Blocks come faster but each holds less, and the proposal does not target throughput.

What should developers check? Any code that assumes 400 millisecond slots or a 60 second blockhash lifetime, plus signing flows that need human approval.

What comes next? Alpenglow, a consensus change. Solana Compass reports testnet and devnet migrations finished on September 24 and 25, with no mainnet date announced.

Sources

Related Reading