Synthetic demo datademo
Every block, transaction, address and hash on this chain is generated from a fixed seed. None of them exists on any network, and none of these values can be looked up anywhere else. The execution trace is real — it is a recorded Noir program — but it is not the execution of the transaction it is published under.
Block
Block 101
UnfinalizedHeight 101 of 102.
- Chain
- demo
- Hash
- 0x72e9ff22eabfba9b6a919946e216c308af8c18ba
- Height
- 101
- Parent
- 0xd43dbec962017960589ef20926d619c26e91508a
- Finality
- Unfinalized
- Transactions
- 2
Transactions in this block
| Debug | Tx hash | Block | From | To / target | Method | Fee | Status |
|---|---|---|---|---|---|---|---|
| Debug | 0xb636…6359 | 101:0 | 0x01c8…d932 | 0x1b31…624c | 0x | 88000 / 200000 mana | Partialprivate-part-succeeded-public-part-succeeded |
| Debug (divergent) | 0x0baa…4a96 | 101:1 | 0x01c8…d932 | 0xae27…671f | 0x1a2b3c4d | 42000 / 100000 mana | Succeeded |
Family extras have no field in the block object yet. §5.2's per-family zone — base fee and blob gas on an EVM chain, checkpoint and epoch on Move, slot and leader on Solana — comes from the adapter, and the published block object carries the chain, the hash, the height, the parent and the transaction list. A transaction already carries its chain-native payload verbatim; a block does not, and that is the field this zone reads when it lands.