Bitcoin Cash Chipnet
Block 302,196
000000002c796cd1a0d1dd90e8f8d07d3dd83a298de1eb51ec92dac18fcbc6c8Confirmation depth
Mined
2026-04-26 21:08:04 UTC · 5016:41:05 ago by Imaginary.cash
Transactions
22
1 coinbase + 21
Size
13.01 KiB
13,325 bytes
Total output
64.52926000 tBCH
sum of every output, coinbase included
Total fees
Unavailable
Not reported for this block.
Median fee rate
Unavailable
Not reported for this block.
Block subsidy
Unavailable
Not reported for this block.
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
- 560 – 627 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/BFee rates are not known on this request, so there is no distribution to draw. Reload to retry
Header
- Block hash
- 000000002c796cd1a0d1dd90e8f8d07d3dd83a298de1eb51ec92dac18fcbc6c8
- Merkle root
- 8fb1587c08ecdaf2f97e0dd5791092abf432c1301a09266d18ef5fd829120e7b
- Previous block · 302,195
- 00000000559d993ad25a667d3e56e85f8a07963bd16db5259e128b0962b79934
- Next block · 302,197
- 000000009d2d31c13a3db94f9f88c6fa2ce99029fd9963a72877d3e039b91851
- Timestamp
- 2026-04-26 21:08:04 UTC
- Median time past
- 2026-04-26 20:11:28 UTC
- Confirmations
- 39,727
- Version
- 536870912 (0x20000000)
- Difficulty
- 1
- Nonce
- 2,820,813,066
- Chain work
- 00000000000000000000000000000000000000000000000002f25154e669f567
- Miner
- Imaginary.cash Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- t /chipnet.imaginary.cash/
Transactions22 in block order
| # | Txid | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | 02bb4be57469…47d3aadb6906 | 1 → 2 | 25.00015000 tBCH | — | — | 144 B | coinbase |
| 1 | 01f03fa922b4…5ec87d39081b | 2 → 2 | 1.98388600 tBCH | — | — | 627 B | CashTokens |
| 2 | 10bc12b22889…a287c1f304b0 | 2 → 2 | 1.98384400 tBCH | — | — | 627 B | CashTokens |
| 3 | 1e588597601a…2611547c6f8e | 2 → 2 | 1.96907600 tBCH | — | — | 627 B | CashTokens |
| 4 | 274e17a29a23…8a9df12ba65d | 2 → 2 | 1.96902000 tBCH | — | — | 627 B | CashTokens |
| 5 | 3b6c33ae2434…e3013e77ee39 | 2 → 2 | 1.96903400 tBCH | — | — | 627 B | CashTokens |
| 6 | 4f4f310d4d03…444a2524fa43 | 2 → 2 | 1.96901300 tBCH | — | — | 627 B | CashTokens |
| 7 | 53f6519c4180…f9cbf72c2ec2 | 2 → 2 | 0.00005000 tBCH | — | — | 560 B | CashTokens |
| 8 | 5a5ea5b59b68…dfc829c0dfe0 | 2 → 2 | 1.96905500 tBCH | — | — | 627 B | CashTokens |
| 9 | 60839e396960…b540f479394d | 2 → 2 | 1.98387900 tBCH | — | — | 627 B | CashTokens |
| 10 | 8ce6db97c374…28d266048c14 | 2 → 2 | 1.98385800 tBCH | — | — | 627 B | CashTokens |
| 11 | 949c56dd312a…841d9dd37266 | 2 → 2 | 1.96906900 tBCH | — | — | 627 B | CashTokens |
| 12 | aa3c37914f7f…aa97d2197f18 | 2 → 2 | 1.98386500 tBCH | — | — | 627 B | CashTokens |
| 13 | ac4d01e430d8…961895f7c856 | 2 → 2 | 1.98383700 tBCH | — | — | 627 B | CashTokens |
| 14 | b66c8de466d1…6a81e56aa6bd | 2 → 2 | 1.96906200 tBCH | — | — | 627 B | CashTokens |
| 15 | be39e69c25d4…cb79c0121fed | 2 → 2 | 1.98387200 tBCH | — | — | 627 B | CashTokens |
| 16 | c41cd1c74a34…ca6625b6a492 | 2 → 2 | 1.96902700 tBCH | — | — | 627 B | CashTokens |
| 17 | cca2b90c98a5…3bf1f348bc7d | 2 → 2 | 1.98389300 tBCH | — | — | 627 B | CashTokens |
| 18 | d2860ae17f79…fd28767d1837 | 2 → 2 | 1.96904800 tBCH | — | — | 627 B | CashTokens |
| 19 | d5bfa0297bef…019cda1458b9 | 2 → 2 | 1.96904100 tBCH | — | — | 627 B | CashTokens |
| 20 | d97df4d7ba94…29d1ab48230b | 2 → 2 | 1.98385100 tBCH | — | — | 627 B | CashTokens |
| 21 | e06965d0c25f…2f1f29ce37f7 | 2 → 2 | 1.98383000 tBCH | — | — | 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.
