Solana speeds up blocks by 17%, but transaction capacity stays the same
Solana reduced its target slot time from 300 milliseconds to 250 milliseconds, accelerating the network clock by about 16.7% so it now targets four slots per second instead of roughly 3.3. The change delivers fresher blockchain state for applications and shorter validator leadership windows, while per-slot work limits are reduced proportionally so overall transaction processing capacity remains roughly unchanged.

Why It Matters
Faster slots can reduce the frequency of stale prices and failed trades for time-sensitive DeFi applications, while leaving the network's total compute and data throughput unchanged. The adjustment also shortens epochs and compresses windows for offline signing and delayed approvals, affecting developer and operational practices.
Key Facts
- previous target slot time: 300 milliseconds
- new target slot time: 250 milliseconds
- approximate speed increase: nearly 17%
- slots per second after change: 4
- validator leadership window before change: 1.2 seconds (four consecutive 300 ms slots)
Solana cut its target slot time from 300 ms to 250 ms, a change that makes the network aim for four slots per second rather than about 3.3. The adjustment reduces the time between blocks so wallets, exchanges and trading applications receive updates more rapidly and validators relinquish leadership sooner. Under the new cadence validators will still lead four consecutive slots, but each leader’s control window falls from 1.2 seconds to one second.
Although the network’s clock runs faster, the update does not raise total transaction capacity. A protocol rule (SIMD-0525) reduces the amount of computation and data permitted in each slot by the same proportion as the shortened slot duration. That leaves the wall-clock ceiling for processing work roughly the same: more slots per second, but less allowed work per slot.
Operational effects include shorter epochs and tighter timelines for human-in-the-loop flows. Because an epoch is fixed at 432,000 slots, its expected length declines from about 36 hours to roughly 30 hours under the 250 ms target. Blockhashes will expire sooner in real time, and there will be less slack for offline signing, delayed approvals and other workflows that rely on longer time windows.
The 250 ms change is the third step in a staged rollout that has moved slot targets from 400 ms to 350 ms, 300 ms and now 250 ms. A further proposal to cut slots to 200 ms — yielding five slots per second and epochs around 24 hours — has been discussed but has no mainnet date; developers say they will proceed only if block-skip rates remain acceptable after this stage.
Keep Reading

Ethereum confirms Glamsterdam dates, but warns 'fake' builders could stall the chain

Corporate treasuries bought just 5,900 bitcoin in 3 months. Other demand signals look weak, too.

Iran’s Strait of Hormuz toll booth ran through a bitcoin exchange, U.S. says

SBI Group backs payments firm dtcpay in $25 million funding round
Original source: CoinDesk