Bitcoin Cash Mainnet
Block 973,778
000000000000000001b71c6fd0d11e429d6a11d0efbc528b3be0f7227fac303aConfirmation depth
Mined
2026-10-21 01:27:30 UTC · 13 d 0 h 48 min 46 s ago by JCBCH
Transactions
18
1 coinbase + 17
Size
15.12 KiB
0.05% of 32 MB, the floor of the adaptive size limit
Total output
664.78806441 BCH
sum of every output, coinbase included
Total fees
33,602 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
- 225 B5
- 226 – 372 B4
- 373 – 643 B4
- 700 – 7,658 B4
- Coinbase
- CashTokens3
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: 1 transaction
- 2 to 3 sat/B: 2 transactions
- 3 to 5 sat/B: 0 transactions
- 5+ sat/B: 1 transaction
6 of 17 (35%) paid exactly the 1 sat/B relay floor, a fee equal to the size in bytes. The highest rate was 75.00 sat/B. Rate is fee divided by size.
Header
- Block hash
- 000000000000000001b71c6fd0d11e429d6a11d0efbc528b3be0f7227fac303a
- Merkle root
- b4d7a0daab419bb31c2a148d95239b9fb8c6f7a615242ba35446c9ef1431cec6
- Previous block · 973,777
- 000000000000000001826abc46de451d477d2a82eebf362466ead6165863475c
- Next block · 973,779
- 000000000000000001f6b5d8e712b8d371eed378eb061213aade4e12fae64892
- Timestamp
- 2026-10-21 01:27:30 UTC
- Median time past
- 2026-10-21 00:50:27 UTC
- Confirmations
- 1,939
- Version
- 639197184 (0x26196000)
- Difficulty
- 467,198,517,329.8504
- Nonce
- 179,516,328
- Chain work
- 00000000000000000000000000000000000000000314d9c19df95bea07aa3423
- Miner
- JCBCH Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- /JCBCH/ b :
Transactions18 in block order
| # | Txid | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | 19d74ef07b40…d3afe4462152 | 1 → 1 | 3.12533602 BCH | — | — | 108 B | coinbase |
| 1 | 0009dcfee94d…61c0bc587042 | 1 → 2 | 0.05714000 BCH | 16,950 sat | 75.00 | 226 B | |
| 2 | 175be56743d2…22600ced8ae4 | 2 → 2 | 0.08697264 BCH | 579 sat | 1.55 | 373 B | |
| 3 | 2f649c275c22…ea54edae6214 | 2 → 2 | 0.56160554 BCH | 374 sat | 1.01 | 372 B | |
| 4 | 41cfe3b546f9…008cf4c0173c | 1 → 2 | 13.12819996 BCH | 228 sat | 1.01 | 225 B | |
| 5 | 5df18eca2e18…6aa12116069b | 1 → 2 | 17.23294163 BCH | 595 sat | 2.64 | 225 B | |
| 6 | 606081ea44b5…80cf7af82b76 | 1 → 8 | 0.31998730 BCH | 1,270 sat | 2.96 | 429 B | |
| 7 | a298a65b829f…cbf239dd9579 | 54 → 1 | 5.67790448 BCH | 7,658 sat | 1.00 | 7,658 B | |
| 8 | cadd58af5a17…0d984c447863 | 1 → 2 | 0.05685808 BCH | 226 sat | 1.00 | 226 B | |
| 9 | cd8d24d9332c…e376b316c768 | 3 → 4 | 481.32087246 BCH | 800 sat | 1.24 | 643 B | CashTokens |
| 10 | d3a066fd126d…924cad960917 | 2 → 12 | 2.77935069 BCH | 700 sat | 1.00 | 700 B | |
| 11 | d5a569bcf0d1…35e6d49414fa | 3 → 3 | 0.57100534 BCH | 999 sat | 1.00 | 999 B | CashTokens |
| 12 | da85fbaa858c…c694d25662ae | 2 → 2 | 99.99999624 BCH | 376 sat | 1.01 | 373 B | |
| 13 | dbde001a34c2…72c6c31cf9dc | 1 → 2 | 0.32575457 BCH | 226 sat | 1.00 | 225 B | |
| 14 | e8137f34c80f…623737257bee | 10 → 10 | 2.50491819 BCH | 1,943 sat | 1.00 | 1,943 B | CashTokens |
| 15 | f1d7eb5c6fee…1bb22d8508de | 1 → 2 | 35.82550517 BCH | 226 sat | 1.00 | 225 B | |
| 16 | f2fd5fae62ec…3f7b6219fe83 | 1 → 2 | 0.43876605 BCH | 226 sat | 1.00 | 226 B | |
| 17 | fb28a25016f8…2bcff0de7d31 | 1 → 2 | 0.77495005 BCH | 226 sat | 1.00 | 225 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.