Bitcoin Cash Tempnet (experimental)
Block 351,525
000000000312b532589bec2f01cda97d1f504c4ff3fc04cc15b8a61a3c6a50d4Confirmation depth
Mined
2026-11-01 10:24:01 UTC · 11 h ago by } ' .\)p
Transactions
25
1 coinbase + 24
Size
7.83 KiB
8,014 bytes; the size limit is not reported for this network
Total output
2.52916800 tBCH
sum of every output, coinbase included
Total fees
20,700 sat
paid by 24 non-coinbase transactions
Median fee rate
3.01 sat/B
24 of 24 non-coinbase transactions in this block
Block subsidy
25.00000000 tBCH
era 1; the coinbase adds the fees
The block as tiles
25 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 B16
- 355 – 476 B4
- 482 – 803 B4
- Coinbase
- CashTokens7
Colour breaks are this block's size quartiles, excluding the coinbase. A filled triangle in the corner marks CashTokens.
Fee-rate distribution
sat/B, 24 of 24 non-coinbase transactions in this block- 1.0 to 1.01 sat/B: 0 transactions
- 1.01 to 1.5 sat/B: 6 transactions
- 1.5 to 2 sat/B: 1 transaction
- 2 to 3 sat/B: 5 transactions
- 3 to 5 sat/B: 12 transactions
- 5+ sat/B: 0 transactions
0 of 24 (0%) paid exactly the 1 sat/B relay floor, a fee equal to the size in bytes. The highest rate was 4.44 sat/B. Rate is fee divided by size.
Header
- Block hash
- 000000000312b532589bec2f01cda97d1f504c4ff3fc04cc15b8a61a3c6a50d4
- Merkle root
- 0ec5bdd24bbea13631f02cad4f9706d8b40bccf4a335c85a878d20374fe994c4
- Previous block · 351,524
- 0000000021a6f17e17d9e8f8371e28d1906a04e8dcf9c6859150712380a894aa
- Next block · 351,526
- 0000000014ef6886f036d2a22d17dfa50ceee4bb972dfb8b931603262894325a
- Timestamp
- 2026-11-01 10:24:01 UTC
- Median time past
- 2026-11-01 10:20:04 UTC
- Confirmations
- 679
- Version
- 4 (0x00000004)
- Difficulty
- 7.42065909
- Nonce
- 2,972,565,706
- Chain work
- 000000000000000000000000000000000000000000000000a17782c7f2834ccf
- Miner
- } ' .\)p Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- %] P
Transactions25 in block order
| # | Transaction | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | 1 → 1 | 2.50020700 tBCH | — | — | 107 B | coinbase | |
| 1 | 1 → 2 | 0.00236000 tBCH | 500 sat | 2.28 | 219 B | ||
| 2 | 1 → 2 | 0.00044000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 3 | 1 → 2 | 0.00036000 tBCH | 500 sat | 2.28 | 219 B | ||
| 4 | 2 → 3 | 0.00047700 tBCH | 500 sat | 1.04 | 482 B | CashTokens | |
| 5 | 2 → 3 | 0.00997300 tBCH | 500 sat | 1.05 | 476 B | CashTokens | |
| 6 | 1 → 6 | 0.00543000 tBCH | 700 sat | 1.97 | 355 B | ||
| 7 | 2 → 3 | 0.00023800 tBCH | 500 sat | 1.05 | 476 B | CashTokens | |
| 8 | 3 → 4 | 0.00036000 tBCH | 1,000 sat | 1.42 | 706 B | CashTokens | |
| 9 | 2 → 3 | 0.00186300 tBCH | 500 sat | 1.05 | 476 B | CashTokens | |
| 10 | 2 → 1 | 0.00000800 tBCH | 3,000 sat | 3.74 | 803 B | CashTokens | |
| 11 | 1 → 2 | 0.00055000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 12 | 1 → 2 | 0.00184000 tBCH | 500 sat | 2.28 | 219 B | ||
| 13 | 1 → 2 | 0.00055000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 14 | 1 → 2 | 0.00033000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 15 | 1 → 2 | 0.00011000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 16 | 1 → 2 | 0.00033000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 17 | 1 → 2 | 0.00033000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 18 | 1 → 2 | 0.00033000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 19 | 1 → 2 | 0.00044000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 20 | 1 → 2 | 0.00133500 tBCH | 500 sat | 2.28 | 219 B | ||
| 21 | 1 → 2 | 0.00033000 tBCH | 1,000 sat | 4.44 | 225 B | ||
| 22 | 1 → 2 | 0.00037500 tBCH | 500 sat | 2.28 | 219 B | ||
| 23 | 2 → 3 | 0.00049200 tBCH | 500 sat | 1.04 | 482 B | CashTokens | |
| 24 | 1 → 2 | 0.00011000 tBCH | 1,000 sat | 4.44 | 225 B |
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.