Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
SOL Solana adjusts the out-blocking time target to 350 milliseconds: Detailed explanation of phased deployment
Solana is adjusting the out-blocking time target to 350 milliseconds through phased network deployment. This move aims to shorten the interval between generation and confirmation of blocks on the chain, thereby accelerating the final confirmation of transactions, and is part of Solana's ongoing efforts to pursue faster settlement.
Changes caused by Solana's 350-millisecond block time goal
The block time refers to the fixed window for the leader verification node to generate a block. Shorter block-out times mean that blocks are generated and confirmed more frequently, and network leaders rotate faster. Solana's reduced block time upgrade page sets 350 milliseconds as the target for the current phase.
This adjustment was introduced in stages and was not an immediate switch to the entire network. According to early telemetry data, 350 milliseconds is the intermediate node to the final goal of 200 milliseconds, and the initial data will be used to assess whether the network can maintain a more compact time rhythm.
Solana pursues lower block times to shorten the time lag between submitting a transaction and packaging the transaction into a block. The technical details of this reduction process are recorded in the protocol improvement process, which is described in detail in the relevant improvement documents.
What faster block-out times mean for users, verification nodes and markets
For users and applications, tighter exit intervals can reduce perceived latency: transactions, redemption, and decentralized application interactions can all be confirmed in less time. This speed of response has been the key to Solana's market narrative in terms of speed and user experience, and is also the performance advantage behind dynamics such as increased ETF market attention.
But this poses challenges for the verification node. As the pace of time tightens, verifying node performance and hardware readiness becomes more critical, as operators need to complete block generation and broadcasting in less time. Phased deployment is precisely to expose problems before these pressures spread to the entire network.
Advantages coexist with execution requirements. Faster confirmation speeds can improve the user experience for traders and protocols-such needs have driven large capital inflows into related products-but only if the verification node infrastructure can keep up with shorter withdrawal times.
Points to pay attention to in phased deployment
Since deployment is phased, the signals released in the short term are testing, observation and gradual expansion, rather than a one-time full activation. Solana records these steps through regular development logs, which are detailed in the relevant development logs.
The main risks during deployment are reliability and coordination: Verify that nodes can operate stably at a pace of 350 milliseconds to avoid missing blocks or falling stability. This is the trade-off point for the phased advancement intended to be exposed early.
To observers, performance is more important than the goal itself. Specific developments worthy of attention include verifying the readiness of nodes at each stage, whether the network can maintain more compact telemetry data, and whether there is a confirmation signal of progress towards the final 200-millisecond target.
