Confirmed transaction 820b7a7fca0a93fe2cec2c8d8caf87f8aeeb69077a2e7ca182ef41 25291f6bf5 Status
Confirmed154,199 confirmations Value flow Ribbon height is proportional to value. Value flow: 1 input to 3 outputs Coinbase 6.25650858 BCH; to Output 0 · OP_RETURN 0.00000000 BCH; Output 1 · P2PKH 6.25650858 BCH; Output 2 · OP_RETURN 0.00000000 BCH; 100.0% Coinbase 6.25650858 BCH new coins plus the block's fees Output 0 · OP_RETURN 0.00000000 BCH script 27ed3fae15…59e14b21 unspent Output 1 · P2PKH 6.25650858 BCH bitcoincash:qrcuqadq…xw4gmv6p spent Output 2 · OP_RETURN 0.00000000 BCH script 11ca94c370…2d485844 unspent Value flow: 1 input to 3 outputs Coinbase 6.25650858 BCH; to Output 0 · OP_RETURN 0.00000000 BCH; Output 1 · P2PKH 6.25650858 BCH; Output 2 · OP_RETURN 0.00000000 BCH; in 0 out 0 out 1 out 2 Coinbase: 6.25650858 BCH of new coins and fees to 3 outputs.
Settlement check Input total
Coinbase
no inputs spent; new coins plus fees
Output total
6.25650858
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.25650858 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: “f/ViaBTC/BCHN/Mined by 7u64i4pg/,mm5Sdx8…”
Unlocking script · 98 bytes
<0x66810c>
<0x2f5669614254432f4243484e2f4d696e65642062792037753634693470672f>
<0xfabe6d6d35d253fc6478383ec00c81594fc5d19f0fe52220f7385e6d0d4f229434d157831000000000000000>
<0x15f2cb0017c9439e03cfc81cd0212b01> 0366810c1f2f5669614254432f4243484e2f4d696e65642062792037753634693470672f2cfabe6d6d35d253fc6478383ec00c81594fc5d19f0fe52220f7385e6d0d4f229434d1578310000000000000001015f2cb0017c9439e03cfc81cd0212b01
Outputs3 · 6.25650858 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.25650858 BCH ‹/› Scripts 2 script 11ca94c370…2d485844 Unspent0.00000000 BCH ‹/› Scripts Locking script Metadata output: “)RSKBLOCK:>Iof9!]sU^3$X…”
Locking script bytes · 43 bytes
OP_RETURN
<0x52534b424c4f434b3a3e496f806639a9217f5d7389551cf59e5ee28bfddb00faeb8a33b4240058b5d2> 6a2952534b424c4f434b3a3e496f806639a9217f5d7389551cf59e5ee28bfddb00faeb8a33b4240058b5d2
Position in block 819,558 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 83 Merkle proof The proof lists the sibling hashes that lift this transaction to the Merkle root in block 819,558'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 010000000000000000000000000000000000000000000000000000000000000000ffffffff620366810c1f2f5669614254432f4243484e2f4d696e65642062792037753634693470672f2cfabe6d6d35d253fc6478383ec00c81594fc5d19f0fe52220f7385e6d0d4f229434d1578310000000000000001015f2cb0017c9439e03cfc81cd0212b01ffffffff03000000000000000027…7f5d7389551cf59e5ee28bfddb00faeb8a33b4240058b5d200000000 Show full hex 01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff620366810c1f2f5669614254432f4243484e2f4d696e65642062792037753634693470672f2cfabe6d6d35d253fc6478383ec00c81594fc5d19f0fe52220f7385e6d0d4f229434d1578310000000000000001015f2cb0017c9439e03cfc81cd0212b01ffffffff030000000000000000276a257342434800fc609736388585e77dc106885dd401b1dab7be87e61a3597239db9d0483e9a46aaac4a25000000001976a914f1c075a01882ae0972f95d3a4177c86c852b7d9188ac00000000000000002b6a2952534b424c4f434b3a3e496f806639a9217f5d7389551cf59e5ee28bfddb00faeb8a33b4240058b5d200000000 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...