Detected delay history
Drag the timeline handles to zoom, or drag the selected window to pan. Arrow keys move a focused handle; Shift moves it by a week. The line connects detected header updates for visual guidance; intervening values are unverified. Each update governs the successor block.
Transition start & end times
Nine episodes from fully scanned transition windows. Start and end mark the first and last observed millisecond-delay update, including reversals; the final value may have been reached earlier. Times are UTC.
| Delay (ms) | Start (UTC) | End (UTC) | Duration | Updates | Chart |
|---|---|---|---|---|---|
| Loading transition summary… | |||||
The first episode includes activation at 2,000 ms. This detailed scan captures changes missed by the broader chart scan; the chart retains its original observations. Full-history coverage remains incomplete. Download transition CSV · Detailed scan coverage
How ACP-226 works
ACP-226 lets validators adjust the minimum time between EVM blocks in milliseconds. Each builder moves a shared header value toward its preferred delay, within a per-block limit. A change applies to the next block.
The implementation uses integer arithmetic. At C-Chain activation, q began at 7,970,124 (about 2,000 ms); each block can change q by at most 200. Roughly 3,600 maximum-size moves halve or double the delay.
A minimum is a timing floor, not a promise of that block rate: consensus, transaction load and scheduling can make intervals longer. Lowering it permits faster blocks without directly raising the gas-throughput target.
Headers expose the shared result, not every validator’s private target. Millisecond timestamps enable sub-second timing while preserving the traditional seconds timestamp.
Read the ACP-226 specification. For the separate price floor, see Minimum Gas Fee · ACP-283.
Evidence & coverage
This page uses the supplied all_detected_delay_changes.csv, including its activation row. The source scan starts on 1 November 2025; the first recorded ACP-226 state is 19 November 2025.
The scan sampled every 4,096 blocks and refined differing endpoints to adjacent linked headers. Equal-endpoint intervals can hide reversals. This is a non-exhaustive inventory of detected changes, not a complete block-by-block timeline.
Inspect detected changes
| Update time (UTC) | Header block | Delay (ms) | First governed block |
|---|