Bitcoin Cash Tempnet (experimental)
Block 287,826
000000000885cf7eb6f6533498d51414049ba64989dc6f0c01b1250614b92eddConfirmation depth
Mined
2026-01-10 08:30:35 UTC · 304 d 5 h 15 min 40 s ago by chipnet.bch.ninja
Transactions
16
1 coinbase + 15
Size
9.22 KiB
9,445 bytes; the size limit is not reported for this network
Total output
28.16661252 tBCH
sum of every output, coinbase included
Total fees
0 sat
paid by 15 non-coinbase transactions
Median fee rate
0.00 sat/B
15 of 15 non-coinbase transactions in this block
Block subsidy
25.00000000 tBCH
era 1; the coinbase adds the fees
The block as tiles
16 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
- 617 B15
- Coinbase
- CashTokens15
Colour breaks are this block's size quartiles, excluding the coinbase. A filled triangle in the corner marks CashTokens.
Fee-rate distribution
sat/B, 15 of 15 non-coinbase transactions in this block- < 1 sat/B: 15 transactions
- 1.0 to 1.01 sat/B: 0 transactions
- 1.01 to 1.5 sat/B: 0 transactions
- 1.5 to 2 sat/B: 0 transactions
- 2 to 3 sat/B: 0 transactions
- 3 to 5 sat/B: 0 transactions
- 5+ sat/B: 0 transactions
0 of 15 (0%) paid exactly the 1 sat/B relay floor, a fee equal to the size in bytes. The highest rate was 0.00 sat/B. Rate is fee divided by size.
Header
- Block hash
- 000000000885cf7eb6f6533498d51414049ba64989dc6f0c01b1250614b92edd
- Merkle root
- 860d646534088c41332d782b09accc14109d0d1f1b62d6503eca3d29360ee4a9
- Previous block · 287,825
- 0000000027e9dd4f1b9dfb42594f78dc10a816d9230986a6361c45428c912914
- Next block · 287,827
- 000000001a51798e4d2e88830ba66daec78378de1444088bed0588d6295f7648
- Timestamp
- 2026-01-10 08:30:35 UTC
- Median time past
- 2026-01-10 07:30:01 UTC
- Confirmations
- 76,923
- Version
- 536870912 (0x20000000)
- Difficulty
- 4.56609477
- Nonce
- 1,362,135,354
- Chain work
- 000000000000000000000000000000000000000000000000021a110ca2543f9e
- Miner
- chipnet.bch.ninja Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- Rd /chipnet.bch.ninja/
Transactions16 in block order
| # | Txid | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | dc423a6d24ff…8f121e837361 | 1 → 1 | 25.00010500 tBCH | — | — | 109 B | coinbase |
| 1 | 06e01af0ea23…7923ecd51e83 | 2 → 2 | 0.00208656 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 2 | 1f5e627093fd…6c79620283d9 | 2 → 2 | 0.99201100 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 3 | 212a22ee7188…a705af2ca9c4 | 2 → 2 | 0.02892882 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 4 | 3d5e9fe75a32…bf87b1a72c71 | 2 → 2 | 0.03786230 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 5 | 56fe0920471d…fa9e9cd9faa7 | 2 → 2 | 0.05091572 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 6 | 6333da3928b3…71af2eebe1af | 2 → 2 | 0.03192260 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 7 | 6838fa09730b…2fd0160d6dfe | 2 → 2 | 0.00037050 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 8 | 6f5e437436eb…e9860cc8d718 | 2 → 2 | 0.99276300 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 9 | 75428f5c5df6…4d75f008a8f3 | 2 → 2 | 0.00151141 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 10 | 823ce4585fbd…2ef1266a1720 | 2 → 2 | 0.97350400 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 11 | 912762dd884c…a0a8d160a7a2 | 2 → 2 | 0.00281918 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 12 | 956665025574…c38ae0b184d8 | 2 → 2 | 0.00043568 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 13 | b96b7be8d974…d603aa9a6d61 | 2 → 2 | 0.00163543 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 14 | c9647d220fbd…8d69a8ac6da7 | 2 → 2 | 0.04757766 tBCH | 0 sat | 0.00 | 617 B | CashTokens |
| 15 | e4af028084aa…dff25b3afba8 | 2 → 2 | 0.00216366 tBCH | 0 sat | 0.00 | 617 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.
