Chapter 04 · One order
Keep every block.
Agree on one order.
Each Kaspa block points at every recent block its miner could see. The rule called then reads that web the same way on every computer and lines all of it up.
selected chainblue blocks it mergesred blocks, if any
Point at a block to see which blocks it points at.
Real blocks, not a simulation.
How the order is built
Each block names one selected parent, the parent with the most blue work behind it. Following those links gives a spine through the web, the selected chain (the deep-blue squares). Each chain block merges the blocks it saw that its selected parent had not: its mergeset. The order is: everything before, then the mergeset sorted by accumulated work, then the chain block itself.
This page rebuilds that order in your browser from fields the node publishes for every block: the chain flag, selected parent, mergeset and blue work. A node’s own virtual-chain call is the authority. Blocks the network hasn’t merged yet are shown as waiting.
A block stays blue if, among the blocks it could not have seen, at most k are blue. Kaspa sets k from the block rate and a worst-case network delay. Mainnet runs GHOSTDAG; DAGKnight is the planned successor that adapts to the network instead (see The race).
What to watch for
- Watch. The blocks line up by themselves, then start again.
- Drag “Scrub” to move between the web and the line.
- Tap any block to see which blocks it points at.
The same rule, walked slowly
G → P0 → P → Q → R → S → M → W → T → U → V
The sandbox is the demo above: ten seconds of real blocks, ordered by this same rule.
The same order, replayed second by second as it settles: Blue tide, on the deep page.
The payment this order settles, through all eight stages of its life: one payment, end to end.
Hold one back
12H3456
Waiting for blocks from the feed…
Blue means well connected. Red means ordered late.
Teaching model. Real colors come from block data.
The one sentenceKeep every block, then let one rule read the web the same way on every computer: that is the whole trick.
The exact version
The same chapter with the workings shown: the derivations, the edge cases, and the numbers behind the plain version.
Payments don’t queue: see it
Payments in parallel blocks don’t queue.
on the waywaiting its turndone
Kaspa tracks money as separate coins, the way Bitcoin does, rather than one balance per account. Payments that land in parallel blocks don’t have to wait for each other.