Measured on Robinhood Chain
Two clocks, and only one of them stops
Robinhood Chain produces a block every 0.101 s, without pause. The exchange that decides what these assets are worth is matching orders 18.7% of the time. Everything below is read from the chain or computed by js/sessions.js, which builds the exchange calendar from its published rules and checks itself against known dates before any of this runs.
Where the clock goes
Where the transfers go
Transfers per hour of each kind of time
The share above is not the finding. The four classes have wildly different durations, so “most transfers happen while the market is shut” would be true of a market that traded perfectly evenly. A rate has its denominator built in.
What this does and does not say
It does not say the on-chain price is wrong while the exchange is shut. It says there is nothing for it to be wrong about: for 81% of the clock there is no auction in the underlying anywhere in the world, and any number quoted then is an opinion about what the auction will say when it reopens.
That is a normal state of affairs for a derivative, and it is priced accordingly everywhere it is acknowledged. What is not normal is quoting it with no marker. Every front page in this category prints a share price and none of them prints which clock it was read on.
The chain’s own memory
Worth knowing if you intend to check any of this yourself. The public node answers
eth_getLogs from block zero — 127 days of complete event history —
and refuses a state question at any block older than
10 minutes with
metadata is not found. 6,031 blocks
of state, against 54m blocks of logs.
That asymmetry is why everything on this site is built from events and from the latest state, never from historical state, and it is why the Bar contract records its own price history rather than leaving it to be reconstructed.
The chain was not always this fast
A single “seconds per block” figure would be wrong about one end of this chain or the other. From block 1 it ran at about two minutes a block for two months; from block 4.5m onward it runs at a tenth of a second and has not varied since.
| Block | Date | s / block |
|---|---|---|
| 1 | 2026-04-30 | 117.9755 |
| 4.5m | 2026-07-08 | 0.1003 |
| 9.1m | 2026-07-13 | 0.1003 |
| 14m | 2026-07-19 | 0.1004 |
| 18m | 2026-07-24 | 0.1003 |
| 23m | 2026-07-29 | 0.1002 |
| 27m | 2026-08-04 | 0.1003 |
| 32m | 2026-08-09 | 0.1003 |
| 36m | 2026-08-14 | 0.1003 |
| 41m | 2026-08-19 | 0.1003 |
| 45m | 2026-08-25 | 0.1003 |
| 50m | 2026-08-30 | 0.1012 |
Averaged over the whole chain the answer is 0.202 s; over the last hundred thousand blocks it is 0.1012 s. The site quotes the second, and the sampling for every measurement here is restricted to the fast range for the same reason — uniform in block number is uniform in time only when the block time is constant.