blockspace.news

Status: Live since 2026-10-19; first edition 2026-10-20
Site: blockspace.news
Data: Heaviest tokens
Data: Largest inscriptions
Data: Summary API
Data: Protocols API
As of: 2026-10-20

What it is #

blockspace.news is "the day in Bitcoin blockspace, in numbers, from block.space": a daily edition of numbers and links. In its own words, every figure is read from block.space's public API, and nothing is estimated.

Status #

Live, as of 2026-10-20. The project list marks it live from 2026-10-19. The first edition appeared at 00:15 UTC on 2026-10-20.

How it works #

Each day at 00:15 UTC the site saves a snapshot of block.space's public API (https://block.space/api/meter, /api/summary and /api/protocols, and the top 100 of /api/largest-inscriptions and /api/heaviest-tokens). An edition is the difference between that day's snapshot and the one before:

the books height then and now, and the blocks written in between;
the Book A bytes added per family, largest first;
new entrants to the 100 largest inscriptions on the largest inscriptions board;
the rank moves in the top 100 of the heaviest tokens board.

Every figure is given as of block H, the height the books are written to. Every edition is kept, so the archive holds them all.

Key figures #

The site has no live figure of its own in this wiki. The edition of Tuesday 20 October 2026 compared the 00:15 UTC snapshot with one taken at 14:22 UTC on 2026-10-19. It counted 67 blocks (972,164 to 972,230), 115 MB of blockspace and 310,987 transactions. Between the books at block 972,099 and block 972,199 it found runes adding the most Book A bytes, 39.9 MB, 58.4 % of the day's. It found no new entrants among the 100 largest inscriptions and no moves in the top 100 heaviest tokens.

Links #

The site: https://blockspace.news, with the archive at https://blockspace.news/archive/ and the feed at https://blockspace.news/feed.xml
Its data: block.space's public API and its boards (listed above).

Glossary #

as of block H: The caption rule every block.space ranking follows. H is the one block the holders appendix is synchronised to. Where the ranking was folded at a different height, or the books are written to another, the detail line names those heights too. A number without its height is not shown.
Book A: The inclusive book: the whole transactions bought for a token, shared where shared. When several tokens share a transaction, its bytes divide among them under the Shared Claim Axiom. In the partition it is content + structure + overhead, "bytes bought for you at all", and it is the backing measure. Fees follow Book A.
edition: One day of blockspace.news. A snapshot of block.space's public API is saved each day at 00:15 UTC; an edition is the difference between that day's snapshot and the one before. A rewound or rewritten set of books is reported as "no comparison", never as a negative.
heaviest tokens board: block.space/heaviest-tokens: the 100,000 heaviest tokens by Book A, every byte of every transaction their operations bought, shared where shared. One row is one token whatever the protocol (a sat, a rune, a BRC-20 tick, a Counterparty asset, an alkane), because the measure is bytes, not kind. Toggles switch to Book B and Book C; each family has a tab.
largest inscriptions board: block.space/largest-inscriptions: the 100,000 largest inscriptions by content bytes (Book C), the bytes the inscription bought, not the bytes it shows. A delegate inscription displays another inscription's content and is ranked at the few hundred bytes it bought. Tabs rank the other content families (Counterparty assets, SRC-20, BRC-20, TAP) by the same book, and "by sat" ranks sats instead.
the books: T3, BTI's accounting layer, and what it writes: Book A, Book B and Book C. T3 is a pure function of T1 and T2: it counts the claimants of each byte, splits shared bytes by the ruleset's formula, allocates fees, and writes the book entries and every block's four categories. It can be deleted and recomputed at any time, because the facts live in the layers below it.

FAQ #

Where do the numbers come from? #

Every figure is read from block.space's public API and bounded by the height its books are written to. The site says nothing is estimated, and it makes no prose claims beyond the data.

When does a new edition appear? #

Once a day. A snapshot is taken at 00:15 UTC, and the edition is the difference between that day's snapshot and the one before.

What happens if the books are rewound? #

A rewound or rewritten set of books is reported as "no comparison", never as a negative.

Is there a feed? #

Yes. Each edition has its own page by date, the archive lists them all, and an Atom feed is at /feed.xml.