Coinbase transaction · Bitcoin Cash Mainnet
Status
Coinbase: 3.12694173 BCH of new coins and fees to 3 outputs.
Input total
Coinbase
no inputs spent; new coins plus fees
Output total
3.12694173
BCH, 3 outputs
Miner fee
None
a coinbase pays no fee
Fee rate
—
not applicable
Size
154 B
version 1, locktime 0
CashTokens
None
no token prefix on any output
Coinbase: it creates 3.12694173 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: “" /NiceHash/” Unlocking script · 14 bytes <0x228b0d> 03228b0d2f4e696365486173682f | ||||
| # | Address | Type | Spent | Amount | Scripts |
|---|---|---|---|---|---|
| 0 | script 677241c46b…c337308c | OP_RETURN | Unspent | 0.00000000 BCH | Scripts |
Locking scriptMetadata output: “^zs:” Locking script bytes · 14 bytes OP_RETURN <0x5eb8c2bf157a733a85e20200> 6a0c5eb8c2bf157a733a85e20200 | |||||
| 1 | qq6mvznj…ms4f8vmt | P2PKH | Spent | 3.09567232 BCH | Scripts |
Spent byef229e25158dbe9c87fe7b117f4fd119882f4d389ee698fb2748fe60721716d9 input #0 in block 887,687 Locking script25-byte pay-to-public-key-hash output Locking script bytes · 25 bytes OP_DUP OP_HASH160 <0x35b60a72e1e99309e237e1bf171514ebb3c0bab5> OP_EQUALVERIFY OP_CHECKSIG 76a91435b60a72e1e99309e237e1bf171514ebb3c0bab588ac | |||||
| 2 | pr2hzgk9…kqy4e44m | P2SH | Spent | 0.03126941 BCH | Scripts |
Spent by8272bd1d35c0fc61c80aab42b40a88339a2dde8907b0693f35e746ad04f87b70 input #2 in block 887,701 Locking script23-byte pay-to-script-hash output (20-byte hash) Locking script bytes · 23 bytes OP_HASH160 <0xd57122c5989ec1ab981d73f60702ebdf66afe5d6> OP_EQUAL a914d57122c5989ec1ab981d73f60702ebdf66afe5d687 | |||||
The proof lists the sibling hashes that lift this transaction to the Merkle root in block 887,586's header. Check it offline against that header.
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff0e03228b0d2f4e696365486173682fffffffff0300000000000000000e6a0c5eb8c2bf157a733a85e20200009f7312000000001976a91435b60a72e1e99309e237e1bf171514ebb3c0bab588ac9db62f000000000017a914d57122c5989ec1ab981d73f60702ebdf66afe5d68700000000
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff0e03228b0d2f4e696365486173682fffffffff0300000000000000000e6a0c5eb8c2bf157a733a85e20200009f7312000000001976a91435b60a72e1e99309e237e1bf171514ebb3c0bab588ac9db62f000000000017a914d57122c5989ec1ab981d73f60702ebdf66afe5d68700000000
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...
