Coins split at 155 days since they last moved. We call coins under 155 days short-term and coins at least 155 days old long-term. In BTC, both lines on one scale.
3,746,637 BTC short-term holders (< 155 days) on Oct-25 2026, the last day in this build, measured and published by askthetape.com.
Split the coins our ledger holds by how long they have sat still: under 155 days is a short-term holder, longer is a long-term holder. The split comes from our own copy of the ledger, counted every day since the first block, so you can watch coins move from one side to the other.
| leg | own UTXO lifecycle ledger (it was built once from a public chain archive and has been extended block by block from our own node since 2026-07-23) · age = days since the coin last moved · 155-day cut |
|---|---|
| cadence | daily |
| since | 2009-01-03 |
| hourly window · where it comes from | the events of this window are read from our own node; the ledger they are added to was built once from a public chain archive and has been extended block by block from our own node since 2026-07-23. The events are every output of 0.01 BTC and up that died and every output that was born, read block by block (getblock … 3 with prevout), with the hour it happened. The carrier holds 8,234 hours, 2025-11-16T00:00:00Z → 2026-10-26T06:00:00Z, 343 days deep from a fixed first day and growing every hour. |
| hourly window · how the hours fold | STATE: the LAST hour of a stretch is that stretch's value, split at 155 days since a coin last moved. «N hours» in the window's own header means BUCKETS WITH DATA, not the distance from the first point to the last — the header prints both. Selected spent-output flows are zero in verified no-block hours; ratios, states and other missing observations remain blank. Block counts are a separate series where present, and describe the native node segment only. |
| hourly window · what this ledger cannot see | the ledger does not see outputs below 0.01 BTC — that is 87,146 BTC, 0.433 % of the coins alive on 2026-10-25, measured against what our own node counts as mined (the scheduled subsidy of every block header it holds). It is a threshold, not a fault, and it is the same threshold the daily page carries. |
| hourly window · which price | the hour is priced with the Binance BTC perpetual of our own capture — the price of THAT HOUR. The daily page uses the Bitstamp daily close. The two were measured against each other on this build over 343 days: median 0.5 bp apart, mean 0.7 bp, worst 42.9 bp. Coins born before this window keep the daily close of their birthday, because the hour of their birth is not in the carrier. Second calibration, hour for hour against the public hourly closes of the spot venue (167 hours, measured 2026-09-19): median -0.05 bp, worst 24.46 bp — so the gap in the first number is the 23:00Z hour against a daily close, not one venue against another. A one-off check, not a captured feed. |
| hourly window · one line or two | one line, not two: for this row the hourly rule and the daily page's rule give the same number, and drawing a second line would promise a difference that does not exist. |
| hourly window · judged | This comparison covers the native node segment from 16 November 2025 only: 🩸 12 birth × spend cells on 3 of 344 closed days differ from the daily ledger of our own node — see the judge log; this window is not vouched for until that is explained. Judge run 2026-10-26, 0.3 hours ago. The judge runs daily against the daily ledger of our own node; a day the 35-day carrier no longer holds is not judged rather than counted as a difference. |
| this build | data to Oct-25 2026 |
| policy | no backfill · read it here · export: whole history |
The chart itself is drawn in the browser: turn JavaScript on to hover a day, pick a window and draw your line. The numbers above come from the last build, Oct-26 2026 08:25Z.
What the tape says today · what's new · all 111 metrics