The Live Block Pile
One box per transaction, one chip per value: the block this site measured.
Block height
--
Transactions
--
Outputs With Value
--
Value Moved
--
ADA
Native Assets
--
The slot leader of this block is not measured yet.
Capacity & share
Block size
--
Plutus transactions
--
Native-asset transactions
--
Block fees--
Script TXs--
Bundled TXs--
The Block as a Pile
ReadingThe last twelve measured blocks, oldest on the left. Click one to open it.
- This block
- --
- vs. average
- --
- Rank in view
- --
- Average
- --
Each tile is one transaction, its area the bytes it takes. The shares below it are measured independently, so they overlap, and every row doubles as a filter.
an output carrying ada
a native token entry
a single-unit asset
a bundle of items
the rest of the block
Waiting for the first block.
Connecting to the live block stream.
--
--
Value & outputs
ada--moved by this block
outputs: those carrying ada, and those carrying none
native-asset entries: token entries, and single-unit assets
--
Block space & scripts
bytes--of the block size limit
Each row is a share of this block's transactions; the bar above is its share of the byte limit.
--
Transaction & chip mix
marks--marks drawn for this block
--
The pile as text
Every transaction in the pile is drawn at full strength.
How search, the lenses and the keyboard work
The search highlights instead of filtering: what it matches stays bright, everything else
fades, and not one box leaves the picture. It understands a token name (USDA), an
amount (45), a part of a transaction hash, and a box number (TX 4).
Pointing at or clicking a token chip rings every other chip of the same asset in the block,
and the panel then says in how many outputs and transactions of the block that asset sits.
The strip above the picture shows the last twelve measured blocks, oldest on the left: the height of a bar is its transactions against the busiest block in the view, the number above it is that count, the dashed tick across the bars is their average, and the tail under it is its height. Hovering a mini block compares it with the block before it.
With the picture focused, the arrow keys move in the direction they name: right and left along the boxes, up and down between rows. Enter opens the chips of the box you stand on, Escape steps back out of them and, on the box level, drops the selection. The copy button writes the link to what you are looking at: the block, the lens, and the box you selected as the number the picture prints on it. Such a link reopens that block with that box selected.
The pile above is drawn by what a transaction carries. The mosaic is the same block drawn by how much room each transaction takes: one tile per transaction, its area its size in bytes. The mosaic comes from the block's composition census, the pile from its transaction list — both describe the block this page is showing, and neither is a sample of another one.
The two pictures are linked by the transaction behind the mark: hovering a tile rings the box that stands for the same transaction, hovering a box rings the tile, and clicking a tile opens that transaction in the panel. The five shares below the mosaic are measured independently, so they overlap; each row is also a filter, and marking one dims everything that does not carry that label — in the mosaic and in the pile, never removing a box.
How to read the pile
Show what a box, a chip and a bundle mean
A box is a transaction
Every transaction of the block gets one open box, and the box is as large as its contents need. The label in its corner prints how many outputs it carries, and how many Plutus scripts it runs when it runs any. Boxes keep the order they have inside the block, left to right and top to bottom.
A chip is a value
A green chip is one output that carries ada, and it prints the amount that output holds, not a denomination the page invented. An amber chip is one native asset entry inside an output, a violet one is an asset that exists exactly once. Chips lock into their box as a new block arrives, and the pile then stands still so it can be read.
A bundle is a count
A transaction can carry hundreds of items, and drawing every one of them would make the picture unreadable. Above a dozen items the chips of that transaction are bundled: one object then stands for the number printed on it, so the picture stays complete while the objects stay countable.
What the picture leaves out
Show what this picture does not measure
- Inputs. The pile is drawn from the outputs of each transaction. Which addresses spent which value is not part of it, so a chip says "this transaction produced this value", never "this value came from that address".
- The mempool. Nothing on this deployment samples pending transactions, so no waiting transaction is drawn and none is counted.
- One chip per asset entry. A token chip stands for one asset inside one output, not for one unit of that asset: the quantity is printed in the panel when a chip is selected.
- The NFT reading is a convention. An asset with a quantity of exactly one is drawn as a single-unit asset. The chain does not label NFTs, so a fungible token that happens to exist once looks the same.
- It depends on a measurement. The transaction list comes from the same block census that feeds the rest of this site. When that census has not answered yet, the page says it is reading, and when it fails the page says so instead of drawing an empty pile.
- No timeline. The page shows one block at a time rather than a timeline, and it replaces its pile when the next block is ready. A link that names a block — by height or by hash — opens that block and stays on it, so a link you share keeps showing the block you were reading until the reader asks for the live chain again. Previous/Next step to the nearest block this deployment has stored, which is a way through the stored blocks, not a chart of them.