Bitcoin Cash Chipnet
Block 270,347
000000002c5b47d96ff26e7774026f51b04964b841c49b75384f3a352273b7d0Confirmation depth
Mined
2025-09-10 23:17:29 UTC · 426 d 23 h 19 min 40 s ago by chipnet.bch.ninja
Transactions
21
1 coinbase + 20
Size
12.51 KiB
12,808 bytes; the size limit is not reported for this network
Total output
1182.38574400 tBCH
sum of every output, coinbase included
Total fees
Unavailable
Fees were reported for 0 of 20 transactions, so there is no exact total
Block subsidy
25.00000000 tBCH
era 1; the coinbase adds the fees
The block as tiles
21 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 B14
- 633 B6
- Coinbase
- CashTokens20
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
- 000000002c5b47d96ff26e7774026f51b04964b841c49b75384f3a352273b7d0
- Merkle root
- 43502644a8fbff288070f69020092e22e9d090d01f049878eacb569afbab6013
- Previous block · 270,346
- 000000001765cdd31f27727037fcc0bb7e4a31471e3a0192465024583a78c5a2
- Next block · 270,348
- 0000000019e0ce0b9cc5e45670908229d1b929676021edad4e8faa14be06d421
- Timestamp
- 2025-09-10 23:17:29 UTC
- Median time past
- 2025-09-10 22:17:52 UTC
- Confirmations
- 61,595
- Version
- 536870912 (0x20000000)
- Difficulty
- 4.39861159
- Nonce
- 1,805,637,403
- Chain work
- 000000000000000000000000000000000000000000000000021915c84f0555ba
- Miner
- chipnet.bch.ninja Attributed from readable coinbase text.
- Attribution
- Matched from readable coinbase text
- Coinbase text
- /chipnet.bch.ninja/
Transactions21 in block order
| # | Txid | In / out | Output total | Fee | Rate | Size | Signal |
|---|---|---|---|---|---|---|---|
| 0 | a855c81053ac…2e7ff5b19741 | 1 → 1 | 25.00014000 tBCH | — | — | 109 B | coinbase |
| 1 | 079fc75419c1…821e5575b79f | 2 → 2 | 57.86926270 tBCH | — | — | 630 B | CashTokens |
| 2 | 1a494c76f570…4a6e0e59b479 | 2 → 2 | 57.86933970 tBCH | — | — | 630 B | CashTokens |
| 3 | 243e1cfa3b65…aa1bb97eb8b9 | 2 → 2 | 57.86929070 tBCH | — | — | 633 B | CashTokens |
| 4 | 2519b3191049…2867420d4540 | 2 → 2 | 57.86927670 tBCH | — | — | 630 B | CashTokens |
| 5 | 2aa19a59bb72…b904387541d3 | 2 → 2 | 57.86928370 tBCH | — | — | 630 B | CashTokens |
| 6 | 2c28932e6ac5…601dffa7f421 | 2 → 2 | 57.86922070 tBCH | — | — | 630 B | CashTokens |
| 7 | 2ec366520fa3…04eea51ceb69 | 2 → 2 | 57.86924870 tBCH | — | — | 633 B | CashTokens |
| 8 | 2fe448d39b76…569c7fa38ac6 | 2 → 2 | 57.86931170 tBCH | — | — | 633 B | CashTokens |
| 9 | 3cbcda344a0a…0f133dfb9462 | 2 → 2 | 57.86926970 tBCH | — | — | 633 B | CashTokens |
| 10 | 61f7cc701289…60009cbf9a69 | 2 → 2 | 57.86932570 tBCH | — | — | 630 B | CashTokens |
| 11 | a954c4a6c8a3…9ae5321217bd | 2 → 2 | 57.86930470 tBCH | — | — | 630 B | CashTokens |
| 12 | aa20fb64d007…46ac6a41d684 | 2 → 2 | 57.86929770 tBCH | — | — | 630 B | CashTokens |
| 13 | b5e5f91a0bf5…a23c14cf230a | 2 → 2 | 57.86925570 tBCH | — | — | 630 B | CashTokens |
| 14 | b806cf5f24ab…e19331faeb6d | 2 → 2 | 57.86923470 tBCH | — | — | 630 B | CashTokens |
| 15 | be9cf8bda438…44f074744e63 | 2 → 2 | 57.86921370 tBCH | — | — | 630 B | CashTokens |
| 16 | cfaf5f9b82fa…4a3ab9d81929 | 2 → 2 | 57.86924170 tBCH | — | — | 630 B | CashTokens |
| 17 | d51102afe61f…1596d3938348 | 2 → 2 | 57.86922770 tBCH | — | — | 633 B | CashTokens |
| 18 | e2a2b064b3dd…4f90e902bdc6 | 2 → 2 | 57.86931870 tBCH | — | — | 630 B | CashTokens |
| 19 | ebeeeea17a6b…eb3560675f05 | 2 → 2 | 57.86934670 tBCH | — | — | 630 B | CashTokens |
| 20 | fa2cd2dbfd64…7f3fdc2588e5 | 2 → 2 | 57.86933270 tBCH | — | — | 633 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.