Bitcoin Cash Mainnet
Block 974,602
000000000000000000956f96b0d2c337f47ae336e7bce739c86cd8e2d83fd955Confirmation depth
Mined
2026-10-26 18:03:43 UTC · 9 d 4 h 31 min 1 s ago by JCBCH
Transactions
18
1 coinbase + 17
Size
5.41 KiB
0.02% of 32 MB, the floor of the adaptive size limit
Total output
116.90749138 BCH
sum of every output, coinbase included
Total fees
7,822 sat
paid by 17 non-coinbase transactions
Median fee rate
1.00 sat/B
17 of 17 non-coinbase transactions in this block
Block subsidy
3.12500000 BCH
era 4; the coinbase adds the fees
The block as tiles
18 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
- 219 – 225 B5
- 226 – 271 B5
- 288 – 372 B3
- 374 – 700 B4
- Coinbase
- CashTokens0
Colour breaks are this block's size quartiles, excluding the coinbase. A filled triangle in the corner marks CashTokens.
Fee-rate distribution
sat/B, 17 of 17 non-coinbase transactions in this block- 1.0 to 1.01 sat/B: 11 transactions
- 1.01 to 1.5 sat/B: 2 transactions
- 1.5 to 2 sat/B: 0 transactions
- 2 to 3 sat/B: 2 transactions
- 3 to 5 sat/B: 2 transactions
- 5+ sat/B: 0 transactions
5 of 17 (29%) paid exactly the 1 sat/B relay floor, a fee equal to the size in bytes. The highest rate was 3.25 sat/B. Rate is fee divided by size.
Header
- Block hash
- 000000000000000000956f96b0d2c337f47ae336e7bce739c86cd8e2d83fd955
- Merkle root
- 08294676c4c0c2e330340b21990c6b979a92dc1b41185ecdc1cc426497e57ee3
- Previous block · 974,601
- 0000000000000000024629eb37fb3eea76ac0d8cbd9c06d6e8733e58b145695a
- Next block · 974,603
- 00000000000000000243e95a47699fb11ff34e6a26129dd8a1ba957e0b9d5e26
- Timestamp
- 2026-10-26 18:03:43 UTC
- Median time past
- 2026-10-26 17:19:31 UTC
- Confirmations
- 1,366
- Version
- 648536064 (0x26a7e000)
- Difficulty
- 472,062,044,039.6494
- Nonce
- 838,707,219
- Chain work
- 000000000000000000000000000000000000000003164a2fcdb7cc5c53f98245
- Miner
- JCBCH Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- /JCBCH/ ze z 1
Transactions18 in block order
| # | Txid | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | c02011ae8651…89753be7e9ff | 1 → 1 | 3.12507822 BCH | — | — | 108 B | coinbase |
| 1 | 076c399733e4…c31498fc420f | 2 → 3 | 21.56809751 BCH | 1,305 sat | 3.00 | 435 B | |
| 2 | 2c49d4606cf2…b5bab0afb8c3 | 2 → 2 | 0.13353801 BCH | 748 sat | 2.00 | 374 B | |
| 3 | 3c24e6014cc2…2efe8d42fd1e | 1 → 2 | 0.12086582 BCH | 222 sat | 1.01 | 219 B | |
| 4 | 4beff6fcc65d…75c94d58a6ce | 1 → 2 | 0.15624821 BCH | 226 sat | 1.00 | 225 B | |
| 5 | 521175c32e55…79cabaee4fb1 | 1 → 2 | 0.00864443 BCH | 226 sat | 1.00 | 225 B | |
| 6 | 555e99e4239d…3ba917b49682 | 1 → 2 | 0.01536017 BCH | 226 sat | 1.00 | 226 B | |
| 7 | 58b05ade2edd…f84b7170e23d | 1 → 2 | 0.00304177 BCH | 266 sat | 1.00 | 266 B | |
| 8 | 5ae5f98e217e…1766cfe66da7 | 1 → 2 | 0.24124260 BCH | 226 sat | 1.00 | 226 B | |
| 9 | 67d6b3016d14…a11076601a76 | 1 → 2 | 0.00303564 BCH | 312 sat | 1.00 | 311 B | |
| 10 | 73d771f3743d…6e1e85021571 | 2 → 2 | 90.31900620 BCH | 376 sat | 1.01 | 372 B | |
| 11 | 8b3e3bb7e947…dd51895581a9 | 1 → 3 | 0.00303617 BCH | 272 sat | 1.00 | 271 B | |
| 12 | 93a076b391c1…9b555bf82345 | 1 → 2 | 0.26123374 BCH | 219 sat | 1.00 | 219 B | |
| 13 | 96e75c05b358…4d56ed1d913c | 4 → 3 | 0.31998584 BCH | 1,416 sat | 2.02 | 700 B | |
| 14 | 97bf5206733b…a07e39c5c5ce | 2 → 3 | 0.51738847 BCH | 498 sat | 1.00 | 496 B | |
| 15 | acfee56d96ef…9848fdeff3cb | 1 → 1 | 0.10561677 BCH | 724 sat | 3.25 | 223 B | |
| 16 | aea17a20f314…91c3d1261076 | 1 → 2 | 0.00303889 BCH | 288 sat | 1.00 | 288 B | |
| 17 | fa7159f7f669…d8a8f1580d4e | 1 → 3 | 0.00303292 BCH | 272 sat | 1.00 | 271 B |
Numbered from 0 in block order. Output total in BCH, 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.
