Mainnet

Configured chains

Coinbase transaction · Bitcoin Cash Mainnet

Confirmed transaction

4134be49fec2294c2399abcf58ab8f2de74e94de01589e36c1c0564284d18396

Status

Confirmed280,181 confirmations

Included in

block 694,652 · 2021-07-02 10:29:31 UTC · 5 yr ago

Previous blockNext blockBlock list

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

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

Settlement check

Input total

Coinbase

no inputs spent; new coins plus fees

Output total

6.25684564

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.25684564 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: “| [sz/BTC.com/BCHN/mmTv.1eX|BS 0 L;l3}…”

Unlocking script · 81 bytes

<0x7c990a>
<0xe2875be8>
OP_IFDUP
OP_ROLL
<0x4254432e636f6d2f4243484e2ffabe6d6dffb554bd76119e2ea8f131006558bcd67c420153be09b230daa2e0b9f00d>
037c990a04e2875be8737a2f4254432e636f6d2f4243484e2ffabe6d6dffb554bd76119e2ea8f131006558bcd67c420153be09b230daa2e0b9f00d4c3b02000000020bb56c33a4fc05b97d000000000000

Outputs2 · 6.25684564 BCH

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

Spent by5b8c9aa36697aa8d3feeb8c47cee1070e996f32c45d0c7ccb349a4fac8fedf71 input #5 in block 694,817

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 510b845bb8…3eaab176
OP_RETURN
Unspent0.00000000 BCH
Scripts

Locking scriptMetadata output: “$m4dI]'r lL @J>i 8”

Locking script bytes · 38 bytes

OP_RETURN
<0xb9e11b6d340764495d27720d9f9c6ceffe8d834c0a9e40a84a3ea4cd0269e4e8120af338>
6a24b9e11b6d340764495d27720d9f9c6ceffe8d834c0a9e40a84a3ea4cd0269e4e8120af338
Position in block 694,652Open 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
694,652
Byte offset in block
83
Block hash
00000000000000000153bb9aac74aeeb2b684f6f6140bd9bd08d4d3b167df487
Merkle proof

The proof lists the sibling hashes that lift this transaction to the Merkle root in block 694,652'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

02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff51037c990a04e2875be8737a2f4254432e636f6d2f4243484e2ffabe6d6dffb554bd76119e2ea8f131006558bcd67c420153be09b230daa2e0b9f00d4c3b02000000020bb56c33a4fc05b97d000000000000ffffffff0254304b25000000001976a91459421d4b38bd3d38ef4877aaf53d…9f9c6ceffe8d834c0a9e40a84a3ea4cd0269e4e8120af33800000000
Show full hex
02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff51037c990a04e2875be8737a2f4254432e636f6d2f4243484e2ffabe6d6dffb554bd76119e2ea8f131006558bcd67c420153be09b230daa2e0b9f00d4c3b02000000020bb56c33a4fc05b97d000000000000ffffffff0254304b25000000001976a91459421d4b38bd3d38ef4877aaf53dbfa6b0acdccd88ac0000000000000000266a24b9e11b6d340764495d27720d9f9c6ceffe8d834c0a9e40a84a3ea4cd0269e4e8120af33800000000
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...