Confirmed transaction 3dddab882dc75ebd6443bb9a2a1de74ef15bbff8fd4f930ca227ca 784f3f87a3 Status
Confirmed163,012 confirmations Value flow Ribbon height is proportional to value. Value flow: 1 input to 3 outputs Coinbase 6.25093909 BCH; to Output 0 · OP_RETURN 0.00000000 BCH; Output 1 · P2PKH 6.25093909 BCH; Output 2 · OP_RETURN 0.00000000 BCH; 100.0% Coinbase 6.25093909 BCH new coins plus the block's fees Output 0 · OP_RETURN 0.00000000 BCH script 27ed3fae15…59e14b21 unspent Output 1 · P2PKH 6.25093909 BCH bitcoincash:qrcuqadq…xw4gmv6p spent Output 2 · OP_RETURN 0.00000000 BCH script 234509a0ad…d0f8785e unspent Value flow: 1 input to 3 outputs Coinbase 6.25093909 BCH; to Output 0 · OP_RETURN 0.00000000 BCH; Output 1 · P2PKH 6.25093909 BCH; Output 2 · OP_RETURN 0.00000000 BCH; in 0 out 0 out 1 out 2 Coinbase: 6.25093909 BCH of new coins and fees to 3 outputs.
Settlement check Input total
Coinbase
no inputs spent; new coins plus fees
Output total
6.25093909
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.25093909 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: “d/ViaBTC/BCHN/Mined by 22368425/,mm CTE=…”
Unlocking script · 98 bytes
<0x0e640c>
<0x2f5669614254432f4243484e2f4d696e65642062792032323336383432352f>
<0xfabe6d6d7f90b6eaeb20d54354a18f1e45973dd79b85bc189da98e631b81a6cc1cf267811000000000000000>
<0x4d7dc90021b4761ef537ef6dbd140500> 030e640c1f2f5669614254432f4243484e2f4d696e65642062792032323336383432352f2cfabe6d6d7f90b6eaeb20d54354a18f1e45973dd79b85bc189da98e631b81a6cc1cf267811000000000000000104d7dc90021b4761ef537ef6dbd140500
Outputs3 · 6.25093909 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.25093909 BCH ‹/› Scripts 2 script 234509a0ad…d0f8785e Unspent0.00000000 BCH ‹/› Scripts Locking script Metadata output: “)RSKBLOCK:@TRQR"}f_O&Vt…”
Locking script bytes · 43 bytes
OP_RETURN
<0x52534b424c4f434b3af0405481e1b5fa12a25251e81952a496c8ef227d81b8665f4f04ea26005674ea> 6a2952534b424c4f434b3af0405481e1b5fa12a25251e81952a496c8ef227d81b8665f4f04ea26005674ea
Position in block 812,046 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 812,046'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 010000000000000000000000000000000000000000000000000000000000000000ffffffff62030e640c1f2f5669614254432f4243484e2f4d696e65642062792032323336383432352f2cfabe6d6d7f90b6eaeb20d54354a18f1e45973dd79b85bc189da98e631b81a6cc1cf267811000000000000000104d7dc90021b4761ef537ef6dbd140500ffffffff03000000000000000027…a25251e81952a496c8ef227d81b8665f4f04ea26005674ea00000000 Show full hex 01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff62030e640c1f2f5669614254432f4243484e2f4d696e65642062792032323336383432352f2cfabe6d6d7f90b6eaeb20d54354a18f1e45973dd79b85bc189da98e631b81a6cc1cf267811000000000000000104d7dc90021b4761ef537ef6dbd140500ffffffff030000000000000000276a257342434800fc609736388585e77dc106885dd401b1dab7be87e61a3597239db9d0483e9a46152d4225000000001976a914f1c075a01882ae0972f95d3a4177c86c852b7d9188ac00000000000000002b6a2952534b424c4f434b3af0405481e1b5fa12a25251e81952a496c8ef227d81b8665f4f04ea26005674ea00000000 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...