TLDR
- Solana will reduce its target block time from 250 milliseconds to 200 milliseconds at epoch 1053 on Friday.
- This completes a seven-week series of cuts that started at 400 milliseconds back in August.
- The network will now target five block-production chances per second, up from 2.5 originally.
- Validators face higher voting costs and a shorter window to order transactions, dropping to 800 milliseconds.
- A separate proposal, SIMD-0675, suggests grouping validators by location to speed up block handovers, though it remains unreviewed.
Solana is finishing a major speed upgrade this week. The network will cut its block time to 200 milliseconds at epoch 1053 on Friday, according to Anza, the company behind Solana’s main validator software.
"Just in the last few months Solana has actually gotten twice as fast as it used to be. And we don't mean that in transactions per second, but in the amount of time it takes a transaction to finalize."
200ms 🔜
– @Austin_Federa, co-founder, @DoubleZero at Solana Summit Korea pic.twitter.com/hWZLL0tReq
— Solana (@solana) October 7, 2026
This is the last step in a plan that began in August. Block times have gone from 400 milliseconds down to 350, then 300, then 250, and now 200.
With this change, Solana can produce blocks five times every second. That is double the original rate of 2.5 times per second.
A block is where transactions get recorded. Faster blocks mean trading apps, wallets, and exchanges get updated information more quickly.
What Changes for Validators
The upgrade also limits how much work fits in each block. At 200 milliseconds, a block can hold 30 million compute units. That is down from 37.5 million at the 250-millisecond setting.
Blocks come more often, but each one carries less data. This keeps the network’s total processing power about the same.
Validators produce blocks in groups of four slots in a row. Their window to order transactions will shrink from 1.6 seconds to 800 milliseconds.
This shorter window could reduce chances for validators to delay transactions or take advantage of price changes on other exchanges.
Faster blocks come with costs. Validators who vote on every slot will need to vote about twice as often. This raises their expenses and strains their network connections.
Wallets and apps will also have less time to use a recent blockhash. This is a code that stops transactions from being copied and resent. The shorter window could make manual transaction approvals harder.
Data from Solana Compass shows the current 250-millisecond setting is running slightly slower than planned, averaging 266 to 269 milliseconds. The final 200-millisecond update has already been tested on Solana’s testnet and devnet. Mainnet rollout timing still depends on how often validators miss their turn to produce a block.
A Separate Plan to Speed Up Handovers
Researchers Roger Wattenhofer and Quentin Kniep have proposed a new way to speed up block handovers between validators. Their idea groups validators by physical location so nearby ones take turns in a row.
In their simulation, this cut the average handover delay between honest validators from 36.2 milliseconds to 17.0 milliseconds. No validator gets more turns under this plan, just a different order.
The proposal relies on validators reporting their own location, which cannot be independently verified. The researchers tested what happens if a validator lies about where it is.
One test case, a validator based in Ashburn, Virginia, cut its own delay by claiming to be in São Paulo instead. The improvement was small, about 2.7 milliseconds.
The researchers say most false location reports would actually hurt a validator’s own speed, not help it. This gives validators a reason to report their real location.
Both proposals mentioned here, the location-based scheduling plan and a related registration system, were submitted on September 29. As of October 7, neither had completed review.
The block time reduction, scheduled for Friday, is the one change confirmed to take effect at epoch 1053.
