Bitcoin Cash Chipnet
Block 306,922
000000009ef2591c5b58dc1520eb714b4c0e6ef3f37e4141c257c78d80e2fb90Confirmation depth
Mined
2026-05-22 22:53:33 UTC · 5 mo ago by Chipnet Imaginary
Transactions
31
1 coinbase + 30
Size
18.59 KiB
19,035 bytes; the size limit is not reported for this network
Total output
78.22318000 tBCH
sum of every output, coinbase included
Total fees
Unavailable
Fees were reported for 0 of 30 transactions, so there is no exact total
Block subsidy
25.00000000 tBCH
era 1; the coinbase adds the fees
The block as tiles
31 transactions in block order, left to right; tile area is bytesCoinbase first at top left, then the transactions in the order the miner placed them. Tap or click a tile to open the transaction. On a desktop, hover a tile for its txid and size.
Tile colour, bytes per transaction
- 627 B30
- Coinbase
- CashTokens30
Colour breaks are this block's size quartiles, excluding the coinbase. A filled triangle in the corner marks CashTokens.
Fee-rate distribution
sat/BFee rates are not known on this request, so there is no distribution to draw. Reload to retry
Header
- Block hash
- 000000009ef2591c5b58dc1520eb714b4c0e6ef3f37e4141c257c78d80e2fb90
- Merkle root
- fed8ca6d0eacb2cc1edb9b2f9adc5469369f024db4eda0bfaea3c33957cb3021
- Previous block · 306,921
- 00000000da212a31d540619a909f2ab82c5c6aeb76b46b9189194249e847bc15
- Next block · 306,923
- 000000000eff200946ab439a6fde8498535cde52e1c33d2d8174c2aef99ad13b
- Timestamp
- 2026-05-22 22:53:33 UTC
- Median time past
- 2026-05-22 21:48:10 UTC
- Confirmations
- 23,668
- Version
- 536870912 (0x20000000)
- Difficulty
- 1
- Nonce
- 1,972,392,966
- Chain work
- 00000000000000000000000000000000000000000000000002f273c107577e94
- Miner
- Chipnet Imaginary Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- /chipnet.imaginary.cash/
Transactions31 in block order
| # | Transaction | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | 1 → 2 | 25.00021000 tBCH | — | — | 144 B | coinbase | |
| 1 | 2 → 2 | 1.69484100 tBCH | — | — | 627 B | CashTokens | |
| 2 | 2 → 2 | 1.69485500 tBCH | — | — | 627 B | CashTokens | |
| 3 | 2 → 2 | 1.85327300 tBCH | — | — | 627 B | CashTokens | |
| 4 | 2 → 2 | 1.85333600 tBCH | — | — | 627 B | CashTokens | |
| 5 | 2 → 2 | 1.85330100 tBCH | — | — | 627 B | CashTokens | |
| 6 | 2 → 2 | 1.69492500 tBCH | — | — | 627 B | CashTokens | |
| 7 | 2 → 2 | 1.85328000 tBCH | — | — | 627 B | CashTokens | |
| 8 | 2 → 2 | 1.85335700 tBCH | — | — | 627 B | CashTokens | |
| 9 | 2 → 2 | 1.85329400 tBCH | — | — | 627 B | CashTokens | |
| 10 | 2 → 2 | 1.69486200 tBCH | — | — | 627 B | CashTokens | |
| 11 | 2 → 2 | 1.69491100 tBCH | — | — | 627 B | CashTokens | |
| 12 | 2 → 2 | 1.85328700 tBCH | — | — | 627 B | CashTokens | |
| 13 | 2 → 2 | 1.69487600 tBCH | — | — | 627 B | CashTokens | |
| 14 | 2 → 2 | 1.85325900 tBCH | — | — | 627 B | CashTokens | |
| 15 | 2 → 2 | 1.85330800 tBCH | — | — | 627 B | CashTokens | |
| 16 | 2 → 2 | 1.69489700 tBCH | — | — | 627 B | CashTokens | |
| 17 | 2 → 2 | 1.69489000 tBCH | — | — | 627 B | CashTokens | |
| 18 | 2 → 2 | 1.85332200 tBCH | — | — | 627 B | CashTokens | |
| 19 | 2 → 2 | 1.85332900 tBCH | — | — | 627 B | CashTokens | |
| 20 | 2 → 2 | 1.69491800 tBCH | — | — | 627 B | CashTokens | |
| 21 | 2 → 2 | 1.85335000 tBCH | — | — | 627 B | CashTokens | |
| 22 | 2 → 2 | 1.69484800 tBCH | — | — | 627 B | CashTokens | |
| 23 | 2 → 2 | 1.85331500 tBCH | — | — | 627 B | CashTokens | |
| 24 | 2 → 2 | 1.85334300 tBCH | — | — | 627 B | CashTokens | |
| 25 | 2 → 2 | 1.69486900 tBCH | — | — | 627 B | CashTokens | |
| 26 | 2 → 2 | 1.69488300 tBCH | — | — | 627 B | CashTokens | |
| 27 | 2 → 2 | 1.69493200 tBCH | — | — | 627 B | CashTokens | |
| 28 | 2 → 2 | 1.69490400 tBCH | — | — | 627 B | CashTokens | |
| 29 | 2 → 2 | 1.69493900 tBCH | — | — | 627 B | CashTokens | |
| 30 | 2 → 2 | 1.85326600 tBCH | — | — | 627 B | CashTokens |
Numbered from 0 in block order. Output total in tBCH, fee in satoshis, rate in sat/B.
Data and proofs
Raw block bytes are fetched on demand so this detail page can remain responsive. Use the plain-text or binary route for the complete payload.