Skip to blog content

    Quality Crypto Reporting · Primary Sources Researched

    CryptoWorkPro

    Market context

    Powered by CoinStats APIUpdated 2:51 AM

    BTC-0.27%
    $84,649
    ETH-1.00%
    $2,681
    XRP-0.45%
    $1.49
    SOL-0.38%
    $118.99
    BNB-0.44%
    $768.72
    HBAR-1.38%
    $0.1011
    QNT+2.65%
    $257.77
    TRX-0.20%
    $0.3337
    LINK-2.58%
    $13.93
    XLM-1.52%
    $0.2155
    Back to Blog
    Solana

    Solana Slot Times Now 300ms Live: SIMD-0525 Cuts from 400ms, 200ms Next Without Extra Capacity

    Published September 13, 2026

    Solana mainnet has taken two of four SIMD-0525 slot-time steps, to 300ms. The 200ms target is not live, and shorter slots are not extra capacity.

    Solana mainnet now runs with reduced slot times. Two steps are live: from 400ms down to 350ms, and then to 300ms. The August 27, 2026, Solana Changelog said Mainnet activated the 300ms feature gate.

    A slot is the target time window for producing one block. Solana 300ms slots mean blocks aim to land every 300 milliseconds. The 200ms dashboard confirmed on September 12, 2026, that the 300ms clock is live. Measured averages hovered around 316ms in a one-minute snapshot then.

    Why this matters

    Shorter slots reduce the clock time of any wait that apps count in slots. A 32-slot wait is 12.8 seconds at a 400ms target and 9.6 seconds at a 300ms target. That is arithmetic on the target, not a measured confirmation time and not a guarantee.

    The Solana Foundation upgrade page says users will experience faster confirmation times. That is Foundation language, not a measured user result in this article. The change is designed to keep total work per second roughly the same.

    What SIMD-0525 actually changes

    SIMD-0525, titled Reduce Slot Times, lays out the plan. Authored by Brennan Watt of Anza, it dates to May 1, 2026. Find the spec here.

    The proposal cuts target slot times in four 50ms steps: 400 to 350, 350 to 300, 300 to 250, and 250 to 200ms. Each step uses a feature gate. These gates become effective one epoch after activation.

    • 350ms: iBRL5RuWhw4yqaAZu96RUULHckHTZAoe2b77qaV38JZ
    • 300ms: iBRLL3k18HST852F1Mf3Lv83waTNQmmqvKDxvYGwQFL
    • 250ms: iBRLMc81UjRa8fn8A6eE8bJTnRbgQoPTynM51akENCV
    • 200ms: iBRLjhJnkmDZgNoZRDMW11d8ZV7HvsL3vAyRjZB5npW

    Ticks per slot hold at 64. Leader windows stay four slots. Epochs remain 432,000 slots. Wall-clock epoch length shortens, from about 48 hours at 400ms toward 24 hours at 200ms. Leader windows shrink from 1.6 seconds to 0.8 seconds.

    Key detail: Per-slot work limits drop in proportion to slot time. Compute units, shreds, and budgets scale down. SIMD-0525 states: "Per-slot work limits are reduced in proportion to the target slot time so the corresponding wall-clock rate remains approximately unchanged."

    Confirmed rollout status

    The Solana Changelog for August 20, 2026, reported mainnet's drop to 350ms via gate iBRL5RuWhw4yqaAZu96RUULHckHTZAoe2b77qaV38JZ. Check it on the explorer.

    August 27, 2026, changelog noted activation of the 300ms gate: iBRLL3k18HST852F1Mf3Lv83waTNQmmqvKDxvYGwQFL. View here.

    The upgrade page, updated August 2026, calls this pending feature activation despite two steps live. It references SIMD discussion 469 and SIMD-0525 as approved. Yet the SIMD-0525 file header lists status as Draft. This labeling mismatch persists.

    The 250ms and 200ms steps await scheduling on mainnet. Testnet hit 200ms; devnet reached 250ms per the August 20 changelog.

    Shorter slots are not more capacity

    Shorter slots keep total blockspace about the same. Blocks arrive more often, but each carries less work. The 200ms dashboard says the same: total blockspace stays the same, and blocks just come more often.

    Measured slot time can vary from target due to skips, load, or client versions. A skip rate occurs when a leader misses its slot. No extra transactions per second emerge automatically. Wall-clock throughput stays level by design.

    What remains unknown

    Activation epochs for 250ms and 200ms lack dates. Anza's Agave v4.2 schedule is tentative. The network can pause if block skip rates rise. Feature gates activated do not mean instant effect; they kick in next epoch.

    Live metrics shift constantly. The dashboard snapshot showed 316ms average, not the 300ms target.

    What to watch next

    Track changelogs and the dashboard for 250ms mainnet activation. Watch skip rates as steps progress. Developers should test slot-based logic at shorter durations. Validators upgrade via Agave releases.

    SIMD-0525 formal PR lives here. Earlier talk in discussion 469.

    Sources and disclosures

    The facts in this story come from the linked official records. Other news coverage is not the evidence for these claims. This report is not investment, legal, or security advice. The featured image is a generated conceptual illustration, not a photograph of a real event. The 200ms dashboard figures cited as live snapshots were checked on September 12, 2026, and can change.