Bitcoin Cash Tempnet (experimental)
Block 268,962
000000001247363f977d04de4acc99a3d9f4c1e5e29a39f493ef1c423594b71aConfirmation depth
Mined
2025-09-01 08:59:27 UTC · 14 mo ago by chipnet.bch.ninja
Transactions
22
1 coinbase + 21
Size
13.11 KiB
13,420 bytes; the size limit is not reported for this network
Total output
195.31217770 tBCH
sum of every output, coinbase included
Total fees
0 sat
paid by 21 non-coinbase transactions
Median fee rate
0.00 sat/B
21 of 21 non-coinbase transactions in this block
Block subsidy
25.00000000 tBCH
era 1; the coinbase adds the fees
The block as tiles
22 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
- 630 B21
- Coinbase
- CashTokens21
Colour breaks are this block's size quartiles, excluding the coinbase. A filled triangle in the corner marks CashTokens.
Fee-rate distribution
sat/B, 21 of 21 non-coinbase transactions in this block- < 1 sat/B: 21 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 21 (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
- 000000001247363f977d04de4acc99a3d9f4c1e5e29a39f493ef1c423594b71a
- Merkle root
- 70e99a8f6ad9fbbe05753d7602c90d89aac739bbb73e40c411b0b1cdbaf408a9
- Previous block · 268,961
- 00000000496c8f327c3de8a39f732286b82eb8b7dd4e273cc682e1173a2832ff
- Next block · 268,963
- 0000000052bcd48a1b25527ff5c792d08e1926414c20a22ef5c04bf12c3bea28
- Timestamp
- 2025-09-01 08:59:27 UTC
- Median time past
- 2025-09-01 08:09:49 UTC
- Confirmations
- 84,256
- Version
- 536870912 (0x20000000)
- Difficulty
- 3.07630246
- Nonce
- 2,073,531,148
- Chain work
- 00000000000000000000000000000000000000000000000002190793ff183563
- Miner
- chipnet.bch.ninja Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- /chipnet.bch.ninja/
Transactions22 in block order
| # | Transaction | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | 1 → 1 | 25.00014700 tBCH | — | — | 109 B | coinbase | |
| 1 | 2 → 2 | 8.11015270 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 2 | 2 → 2 | 8.11013870 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 3 | 2 → 2 | 8.11003370 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 4 | 2 → 2 | 8.11008270 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 5 | 2 → 2 | 8.11002670 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 6 | 2 → 2 | 8.11008970 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 7 | 2 → 2 | 8.11011070 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 8 | 2 → 2 | 8.11010370 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 9 | 2 → 2 | 8.11004770 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 10 | 2 → 2 | 8.11013170 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 11 | 2 → 2 | 8.11016670 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 12 | 2 → 2 | 8.11006170 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 13 | 2 → 2 | 8.11015970 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 14 | 2 → 2 | 8.11014570 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 15 | 2 → 2 | 8.11005470 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 16 | 2 → 2 | 8.11011770 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 17 | 2 → 2 | 8.11004070 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 18 | 2 → 2 | 8.11006870 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 19 | 2 → 2 | 8.11012470 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 20 | 2 → 2 | 8.11009670 tBCH | 0 sat | 0.00 | 630 B | CashTokens | |
| 21 | 2 → 2 | 8.11007570 tBCH | 0 sat | 0.00 | 630 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.
