Skip to main content
Uruguay Can

News from across crypto

Solana cuts target slot time to 200 milliseconds

Solana’s final slot-time cut took effect Oct. 9, bringing the target to 200 milliseconds and doubling block opportunities while halving blockhash validity.

Uruguay Can Editorial

Solana cuts target slot time to 200 milliseconds

Solana’s target slot time was 250 milliseconds; on Oct. 9, the final stage of its rollout cut it to 200 milliseconds on mainnet. The Solana Foundation’s upgrade record says the change took effect at the start of epoch 1053, completing four staged reductions from 400 milliseconds. A slot is the window in which a designated validator can add transactions, so the network now targets five block-production opportunities per second, up from 2.5.

What changes for transactions and apps?

More frequent slots can give wallets, exchanges and trading apps new on-chain information sooner, although a 200-millisecond target does not guarantee every block arrives on schedule. The Foundation says each epoch still contains 432,000 slots, so epochs now take about 24 hours rather than roughly 48. The blockhash validity window also shrank in real time: it remains 150 blocks, but now lasts about 30 seconds instead of 60. If you use a wallet flow that waits for manual approval or an offline signature, that leaves less time before a transaction’s blockhash expires.

Does faster block production mean more capacity?

Not necessarily: blocks arrive more often, but each has a tighter compute limit. CoinDesk’s report on the upgrade says the limit falls from 37.5 million compute units per block at 250 milliseconds to 30 million at 200 milliseconds, keeping theoretical processing capacity roughly unchanged. The change is about latency and timing, rather than a simple increase in how much work Solana can process.

The rollout also shortens each validator leader’s uninterrupted stretch for ordering transactions. Validators still produce blocks in groups of four consecutive slots, but that window is now 800 milliseconds, down from 1.6 seconds at the original 400-millisecond target. The shorter window may limit how long one leader controls block ordering; validators also have to submit votes more frequently, while apps that estimate elapsed time from slot numbers need to account for the new rate.

Sources