Bitcoin Cash Tempnet (experimental)
Block 309,241
0000000028aad66c28075081d8d2af01356a5826ce35c9252faf608c9f2152a0Confirmation depth
Mined
2026-06-08 02:01:15 UTC · 155 d 22 h 29 min 45 s ago by chipnet.bch.ninja
Transactions
16
1 coinbase + 15
Size
8.18 KiB
8,379 bytes; the size limit is not reported for this network
Total output
41.36096000 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
- 219 – 394 B4
- 627 B10
- 695 B1
- Coinbase
- CashTokens13
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
- 0000000028aad66c28075081d8d2af01356a5826ce35c9252faf608c9f2152a0
- Merkle root
- 4629b481d61f54750c1e2c64a933289cd7ac37adf37497626ba6404b5818a85d
- Previous block · 309,240
- 000000004c1276e23a691b2d897a986087e3824003cfc76e749ddd46966c1904
- Next block · 309,242
- 000000000c3ad99479e72ac85c60baf51cbf8b4b9ec15c3f0bf5e959a9e56ef2
- Timestamp
- 2026-06-08 02:01:15 UTC
- Median time past
- 2026-06-08 01:16:35 UTC
- Confirmations
- 56,035
- Version
- 536870912 (0x20000000)
- Difficulty
- 3.45727015
- Nonce
- 1,029,999,385
- Chain work
- 00000000000000000000000000000000000000000000000002f2902a0ade21ba
- Miner
- chipnet.bch.ninja Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- /chipnet.bch.ninja/
Transactions16 in block order
| # | Txid | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | 7198f1ae19a5…98d01e7a210c | 1 → 1 | 25.00028000 tBCH | — | — | 107 B | coinbase |
| 1 | 0232e793d395…a9b2c99e3bc7 | 1 → 2 | 0.00563000 tBCH | 0 sat | 0.00 | 219 B | |
| 2 | 0bf25130b18f…f5f8745e19d7 | 2 → 2 | 0.00558000 tBCH | 0 sat | 0.00 | 394 B | CashTokens |
| 3 | 164ac4e61e6c…413e50ee64b3 | 2 → 2 | 1.49750800 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 4 | 348aa7f48765…1dac37ab65f7 | 2 → 2 | 1.76890300 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 5 | 59dcfff6d3e8…ca71975283a5 | 3 → 4 | 0.00580000 tBCH | 0 sat | 0.00 | 695 B | CashTokens |
| 6 | 60527d7a0777…f5a965beb63e | 2 → 2 | 1.76887500 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 7 | 63d6201da72c…ebcfd232c118 | 2 → 2 | 0.00580000 tBCH | 0 sat | 0.00 | 394 B | CashTokens |
| 8 | 7526be118ac4…ee8cc6f4d3cb | 2 → 2 | 1.76889600 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 9 | 77612e05e723…5ea3814b50e6 | 2 → 2 | 1.49750100 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 10 | 794db25f9a5e…d129bd9cb488 | 2 → 2 | 1.49751500 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 11 | c2a39441cd5f…84f3a7914121 | 2 → 2 | 1.49752900 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 12 | d6d79450cc93…1eed7d21d7d2 | 1 → 2 | 0.00585000 tBCH | 0 sat | 0.00 | 219 B | |
| 13 | ebb4494eafdc…3b56a2b7caa0 | 2 → 2 | 1.76888200 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 14 | f473907fe102…7393b4da4341 | 2 → 2 | 1.76888900 tBCH | 0 sat | 0.00 | 627 B | CashTokens |
| 15 | f95fa364ba52…1aa02e2cd3a8 | 2 → 2 | 1.49752200 tBCH | 0 sat | 0.00 | 627 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.
