Confirmed transaction 9fece0d8fc0b3985ffdb76c0babc57f5b16b79f4eef7f95ea5c32e 9890871aae Status
Confirmed160,072 confirmations Value flow Ribbon height is proportional to value. Value flow: 1 input to 3 outputs Coinbase 6.25045063 BCH; to Output 0 · OP_RETURN 0.00000000 BCH; Output 1 · P2PKH 6.25045063 BCH; Output 2 · OP_RETURN 0.00000000 BCH; 100.0% Coinbase 6.25045063 BCH new coins plus the block's fees Output 0 · OP_RETURN 0.00000000 BCH script 27ed3fae15…59e14b21 unspent Output 1 · P2PKH 6.25045063 BCH bitcoincash:qrcuqadq…xw4gmv6p spent Output 2 · OP_RETURN 0.00000000 BCH script dde68c6d18…725669ff unspent Value flow: 1 input to 3 outputs Coinbase 6.25045063 BCH; to Output 0 · OP_RETURN 0.00000000 BCH; Output 1 · P2PKH 6.25045063 BCH; Output 2 · OP_RETURN 0.00000000 BCH; in 0 out 0 out 1 out 2 Coinbase: 6.25045063 BCH of new coins and fees to 3 outputs.
Settlement check Input total
Coinbase
no inputs spent; new coins plus fees
Output total
6.25045063
BCH, 3 outputs
Miner fee
None
a coinbase pays no fee
Size
283 B
version 1, locktime 0
CashTokens
None
no token prefix on any output
Coinbase: it creates 6.25045063 BCH of new coins and fees, so there are no inputs to balance.
# Address and previous output Type Amount Scripts 0 Coinbase creates new coins; no previous output Coinbase — ‹/› Scripts Unlock type Coinbase · Coinbase data: “{k/ViaBTC/BCHN/Mined by pavel885/,mmg Tj…”
Unlocking script · 98 bytes
<0x7b6b0c>
<0x2f5669614254432f4243484e2f4d696e656420627920706176656c3838352f>
<0xfabe6d6dfcc5cf67aab4d2180dec8088fb8054e56af46db7fe0a4a44e1a70823ce105f481000000000000000>
<0x321bca00fca0fdbd74f69a74b4e50200> 037b6b0c1f2f5669614254432f4243484e2f4d696e656420627920706176656c3838352f2cfabe6d6dfcc5cf67aab4d2180dec8088fb8054e56af46db7fe0a4a44e1a70823ce105f48100000000000000010321bca00fca0fdbd74f69a74b4e50200
Outputs3 · 6.25045063 BCH Spend states looked up for 3 of 3 outputs: 1 spent, 2 unspent. # Address Type Spent Amount Scripts 0 script 27ed3fae15…59e14b21 Unspent0.00000000 BCH ‹/› Scripts Locking script Metadata output: “%sBCH`68}]5#H>F”
Locking script bytes · 39 bytes
OP_RETURN
<0x7342434800fc609736388585e77dc106885dd401b1dab7be87e61a3597239db9d0483e9a46> 6a257342434800fc609736388585e77dc106885dd401b1dab7be87e61a3597239db9d0483e9a46 1 qrcuqadq…xw4gmv6p Spent6.25045063 BCH ‹/› Scripts 2 script dde68c6d18…725669ff Unspent0.00000000 BCH ‹/› Scripts Locking script Metadata output: “)RSKBLOCK:y{;ox=K;YU'W…”
Locking script bytes · 43 bytes
OP_RETURN
<0x52534b424c4f434b3ae9ec79aecebd7b9d14f53b6ffc78db3dca9f9d934bcf023b59550127005702de> 6a2952534b424c4f434b3ae9ec79aecebd7b9d14f53b6ffc78db3dca9f9d934bcf023b59550127005702de
Position in block 813,947 Open the block The tile strip needs the block's transaction list, which this page does not load. Open the block for its tile grid.
Byte offset in block 81 Merkle proof The proof lists the sibling hashes that lift this transaction to the Merkle root in block 813,947's header. Check it offline against that header.
This page does not load the path itself; the proof download holds it.
Raw transaction283 bytes Copy hex01000000 010000000000000000000000000000000000000000000000000000000000000000ffffffff62037b6b0c1f2f5669614254432f4243484e2f4d696e656420627920706176656c3838352f2cfabe6d6dfcc5cf67aab4d2180dec8088fb8054e56af46db7fe0a4a44e1a70823ce105f48100000000000000010321bca00fca0fdbd74f69a74b4e50200ffffffff03000000000000000027…14f53b6ffc78db3dca9f9d934bcf023b59550127005702de00000000 Show full hex 01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff62037b6b0c1f2f5669614254432f4243484e2f4d696e656420627920706176656c3838352f2cfabe6d6dfcc5cf67aab4d2180dec8088fb8054e56af46db7fe0a4a44e1a70823ce105f48100000000000000010321bca00fca0fdbd74f69a74b4e50200ffffffff030000000000000000276a257342434800fc609736388585e77dc106885dd401b1dab7be87e61a3597239db9d0483e9a46476e4125000000001976a914f1c075a01882ae0972f95d3a4177c86c852b7d9188ac00000000000000002b6a2952534b424c4f434b3ae9ec79aecebd7b9d14f53b6ffc78db3dca9f9d934bcf023b59550127005702de00000000 Bitauth scenario libauth wallet template JSON 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.
Source outputs none (coinbase) Show scenario JSON Loading payload...