Mainnet

Coinbase transaction · Bitcoin Cash Mainnet

Confirmed transaction

fafada3bff06a31fbd74ffc19177adf3d26c3de41bc1ccab2d83f09e25b5de40

Status

Confirmed288,218 confirmations

Included in

block 686,340 · 2021-05-04 21:54:35 UTC · 5 yr ago

Previous blockNext blockBlock list

Value flowRibbon height is proportional to value.
Value flow: 1 input to 2 outputsCoinbase 6.25109789 BCH; to Output 0 · P2PKH 6.25109789 BCH; Output 1 · OP_RETURN 0.00000000 BCH;100.0% of input valueCoinbase6.25109789 BCHnew coins plus the block's feesOutput 0 · P2PKH6.25109789 BCHbitcoincash:qpk4hk3w…zf9sur4hspentOutput 1 · OP_RETURN0.00000000 BCHscript ce0207ceb2…48b2fd6cunspent
Value flow: 1 input to 2 outputsCoinbase 6.25109789 BCH; to Output 0 · P2PKH 6.25109789 BCH; Output 1 · OP_RETURN 0.00000000 BCH;in 0out 0out 1

Coinbase: 6.25109789 BCH of new coins and fees to 2 outputs.

Settlement check

Input total

Coinbase

no inputs spent; new coins plus fees

Output total

6.25109789

BCH, 2 outputs

Miner fee

None

a coinbase pays no fee

Fee rate

—

not applicable

Size

231 B

version 1, locktime 0

CashTokens

None

no token prefix on any output

Coinbase: it creates 6.25109789 BCH of new coins and fees, so there are no inputs to balance.

Inputs1

Coinbase input
#Address and previous outputTypeAmountScripts
0Coinbasecreates new coins; no previous outputCoinbase—
Scripts

Unlock typeCoinbase · Coinbase data: “y A$p,A$pbb/BTC.TOP/ByBCHN/mmyt>6C.kALOt…”

Unlocking script · 94 bytes

<0x04790a>
<0xd82470a62cdabc41d82470a4ec000662622f4254432e544f502f42794243484e2ffabe6d6dde7974cfa83e36d607ef19432eb9a2d46b901a4104dfff4ce5037fb2>
UNKNOWN_OPCODE
OP_1NEGATE
<0x748000000000000000b500f5a8b93900>
<0>
<0>
<0>
<0>
<0>
0304790a41d82470a62cdabc41d82470a4ec000662622f4254432e544f502f42794243484e2ffabe6d6dde7974cfa83e36d607ef19432eb9a2d46b901a4104dfff4ce5037fb2f84f10748000000000000000b500f5a8b939000000000000

Outputs2 · 6.25109789 BCH

Spend states looked up for 2 of 2 outputs: 1 spent, 1 unspent.
#AddressTypeSpentAmountScripts
0qpk4hk3w…zf9sur4h
P2PKH
Spent6.25109789 BCH
Scripts

Spent byeee6a46eb0eb2c3f7097ed294030bb0ec073f71a5b3ead27d58c357eb83290e8 input #21 in block 686,620

Locking script25-byte pay-to-public-key-hash output

Locking script bytes · 25 bytes

OP_DUP
OP_HASH160
<0x6d5bda2ee1b2ae0160c17d33f56218c7a1d37fce>
OP_EQUALVERIFY
OP_CHECKSIG
76a9146d5bda2ee1b2ae0160c17d33f56218c7a1d37fce88ac
1script ce0207ceb2…48b2fd6c
OP_RETURN
Unspent0.00000000 BCH
Scripts

Locking scriptMetadata output: “)RSKBLOCK:&Gz:c:pd-2…”

Locking script bytes · 43 bytes

OP_RETURN
<0x52534b424c4f434b3ab62699808f47c17a3ab563953ac7fa70a5c064c79fcc2d0be41fac150032b412>
6a2952534b424c4f434b3ab62699808f47c17a3ab563953ac7fa70a5c064c79fcc2d0be41fac150032b412
Position in block 686,340Open the block

The tile strip needs the block's transaction list, which this page does not load. Open the block for its tile grid.

Block height
686,340
Byte offset in block
81
Merkle proof

The proof lists the sibling hashes that lift this transaction to the Merkle root in block 686,340's header. Check it offline against that header.

This page does not load the path itself; the proof download holds it.

Raw transaction231 bytes

01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff5e0304790a41d82470a62cdabc41d82470a4ec000662622f4254432e544f502f42794243484e2ffabe6d6dde7974cfa83e36d607ef19432eb9a2d46b901a4104dfff4ce5037fb2f84f10748000000000000000b500f5a8b939000000000000ffffffff021d6b4225000000001976a9146d…3ab563953ac7fa70a5c064c79fcc2d0be41fac150032b41200000000
Show full hex
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff5e0304790a41d82470a62cdabc41d82470a4ec000662622f4254432e544f502f42794243484e2ffabe6d6dde7974cfa83e36d607ef19432eb9a2d46b901a4104dfff4ce5037fb2f84f10748000000000000000b500f5a8b939000000000000ffffffff021d6b4225000000001976a9146d5bda2ee1b2ae0160c17d33f56218c7a1d37fce88ac00000000000000002b6a2952534b424c4f434b3ab62699808f47c17a3ab563953ac7fa70a5c064c79fcc2d0be41fac150032b41200000000

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...