Coinbase transaction · Bitcoin Cash Mainnet
Status
Coinbase: 25.11880620 BCH of new coins and fees to 2 outputs.
Input total
Coinbase
no inputs spent; new coins plus fees
Output total
25.11880620
BCH, 2 outputs
Miner fee
None
a coinbase pays no fee
Fee rate
—
not applicable
Size
167 B
version 1, locktime 0
CashTokens
None
no token prefix on any output
Coinbase: it creates 25.11880620 BCH of new coins and fees, so there are no inputs to balance.
| # | Address and previous output | Type | Amount | Scripts |
|---|---|---|---|---|
| 0 | Coinbasecreates new coins; no previous output | Coinbase | — | Scripts |
Unlock typeCoinbase · Coinbase data: “Y/P2SH/w U; lz ckpool/Kano…” Unlocking script · 48 bytes <0xf65905> <0x062f503253482f> <0x77102055> <0x3b15b620> <0x1704849d6c7a010000000000> <0x636b706f6f6c052f4b61> OP_2DUP OP_3DUP 03f6590507062f503253482f0477102055043b15b6200c1704849d6c7a0100000000000a636b706f6f6c052f4b616e6f | ||||
| # | Address | Type | Spent | Amount | Scripts |
|---|---|---|---|---|---|
| 0 | qq7mcwxt…j0696xp5 | P2PKH | Spent | 24.89273695 BCH | Scripts |
Spent by9c44f25bab0ea7f60f814b39b5128c9a0c1eb10ded4b9210da54c079c45f1ec4 input #0 in block 350,817 Locking script25-byte pay-to-public-key-hash output Locking script bytes · 25 bytes OP_DUP OP_HASH160 <0x3dbc38cb635600f436290f3270255f0da9d102a2> OP_EQUALVERIFY OP_CHECKSIG 76a9143dbc38cb635600f436290f3270255f0da9d102a288ac | |||||
| 1 | qpealr0h…wc2v82cm | P2PKH | Spent | 0.22606925 BCH | Scripts |
Spent bydde3538a45568ecf9619839988a9f36a8ca0e9360aab5ab30315ddd00a8dea12 input #1 in block 350,948 Locking script25-byte pay-to-public-key-hash output Locking script bytes · 25 bytes OP_DUP OP_HASH160 <0x73df8df7d39dc0a1f651d6107330be85bfd5859e> OP_EQUALVERIFY OP_CHECKSIG 76a91473df8df7d39dc0a1f651d6107330be85bfd5859e88ac | |||||
The proof lists the sibling hashes that lift this transaction to the Merkle root in block 350,710's header. Check it offline against that header.
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff3003f6590507062f503253482f0477102055043b15b6200c1704849d6c7a0100000000000a636b706f6f6c052f4b616e6fffffffff025f4d5f94000000001976a9143dbc38cb635600f436290f3270255f0da9d102a288ac4df45801000000001976a91473df8df7d39dc0a1f651d6107330be85bfd5859e88ac00000000
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff3003f6590507062f503253482f0477102055043b15b6200c1704849d6c7a0100000000000a636b706f6f6c052f4b616e6fffffffff025f4d5f94000000001976a9143dbc38cb635600f436290f3270255f0da9d102a288ac4df45801000000001976a91473df8df7d39dc0a1f651d6107330be85bfd5859e88ac00000000
A scenario bundles this transaction with the outputs it spends, so each unlocking script can be stepped through op by op in Bitauth IDE and its signature check re-run against the exact source outputs.
Loading payload...
