Mainnet

Configured chains

Coinbase transaction · Bitcoin Cash Mainnet

Confirmed transaction

ebc089de778e4495aee1e7dfc8d761b0e8f11d7eec2d494fe6df65cc98d193a8

Status

Confirmed286,496 confirmations

Included in

block 688,401 · 2021-05-17 20:48:20 UTC · 5 yr ago

Previous blockNext blockBlock list

Value flowRibbon height is proportional to value.
Value flow: 1 input to 2 outputsCoinbase 6.30905957 BCH; to Output 0 · P2PKH 6.30905957 BCH; Output 1 · OP_RETURN 0.00000000 BCH;100.0% of input valueCoinbase6.30905957 BCHnew coins plus the block's feesOutput 0 · P2PKH6.30905957 BCHbitcoincash:qpv5y82t…9h5cdsn2spentOutput 1 · OP_RETURN0.00000000 BCHscript da7fd1548e…10462136unspent
Value flow: 1 input to 2 outputsCoinbase 6.30905957 BCH; to Output 0 · P2PKH 6.30905957 BCH; Output 1 · OP_RETURN 0.00000000 BCH;in 0out 0out 1

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

Settlement check

Input total

Coinbase

no inputs spent; new coins plus fees

Output total

6.30905957

BCH, 2 outputs

Miner fee

None

a coinbase pays no fee

Fee rate

—

not applicable

Size

213 B

version 2, locktime 0

CashTokens

None

no token prefix on any output

Coinbase: it creates 6.30905957 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: “(bj/BTC.com/BCHN/mmjI]nww.elJP)YOz l…”

Unlocking script · 81 bytes

<0x11810a>
<0x28eaddbf>
UNKNOWN_OPCODE
OP_RETURN
<0x4254432e636f6d2f4243484e2ffabe6d6dba8b6a91e1498286e85d1f6e77772ec065899f6c4a5029e7594faa957a0a>
0311810a0428eaddbf626a2f4254432e636f6d2f4243484e2ffabe6d6dba8b6a91e1498286e85d1f6e77772ec065899f6c4a5029e7594faa957a0a19ed02000000020bb56c01ebf9931ded030000000000

Outputs2 · 6.30905957 BCH

Spend states looked up for 2 of 2 outputs: 1 spent, 1 unspent.
#AddressTypeSpentAmountScripts
0qpv5y82t…9h5cdsn2
P2PKH
Spent6.30905957 BCH
Scripts

Spent by630db350a82b4e174901bf4893f019709ba8af1f39ffc30b29b1ff09dde8c478 input #2 in block 688,859

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

Locking script bytes · 25 bytes

OP_DUP
OP_HASH160
<0x59421d4b38bd3d38ef4877aaf53dbfa6b0acdccd>
OP_EQUALVERIFY
OP_CHECKSIG
76a91459421d4b38bd3d38ef4877aaf53dbfa6b0acdccd88ac
1script da7fd1548e…10462136
OP_RETURN
Unspent0.00000000 BCH
Scripts

Locking scriptMetadata output: “$m\4mQO%4J[=n”

Locking script bytes · 38 bytes

OP_RETURN
<0xb9e11b6db51e5ca4b7c49eb134d56dc351db8ec6ff4f8625060ced0f344ab55b3d6eae87>
6a24b9e11b6db51e5ca4b7c49eb134d56dc351db8ec6ff4f8625060ced0f344ab55b3d6eae87
Position in block 688,401Open 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
688,401
Byte offset in block
83
Block hash
000000000000000001eff0399a11b146607d77ed3d05fd3d744e58f6e3fca14a
Merkle proof

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

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

Merkle proofBlock header

Raw transaction213 bytes

02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff510311810a0428eaddbf626a2f4254432e636f6d2f4243484e2ffabe6d6dba8b6a91e1498286e85d1f6e77772ec065899f6c4a5029e7594faa957a0a19ed02000000020bb56c01ebf9931ded030000000000ffffffff0265dc9a25000000001976a91459421d4b38bd3d38ef4877aaf53d…34d56dc351db8ec6ff4f8625060ced0f344ab55b3d6eae8700000000
Show full hex
02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff510311810a0428eaddbf626a2f4254432e636f6d2f4243484e2ffabe6d6dba8b6a91e1498286e85d1f6e77772ec065899f6c4a5029e7594faa957a0a19ed02000000020bb56c01ebf9931ded030000000000ffffffff0265dc9a25000000001976a91459421d4b38bd3d38ef4877aaf53dbfa6b0acdccd88ac0000000000000000266a24b9e11b6db51e5ca4b7c49eb134d56dc351db8ec6ff4f8625060ced0f344ab55b3d6eae8700000000
Download HEX encoded txDownload binary tx

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)
Open in Bitauth IDEDownload Bitauth JSON
Show scenario JSON
Loading payload...