Mainnet

Configured chains

Coinbase transaction · Bitcoin Cash Mainnet

Confirmed transaction

43d0166a68faf1ffbc0dff4eaa4f0f4a4e8a285076ed5fd9121ccfe4fc3d27d4

Status

Confirmed503,137 confirmations

Included in

block 470,466 · 2017-06-09 05:18:41 UTC · 9 yr ago

Previous blockNext blockBlock list

Value flowRibbon height is proportional to value.
Value flow: 1 input to 2 outputsCoinbase 13.24793076 BCH; to Output 0 · P2SH 13.24793076 BCH; Output 1 · OP_RETURN 0.00000000 BCH;100.0% of input valueCoinbase13.24793076 BCHnew coins plus the block's feesOutput 0 · P2SH13.24793076 BCHbitcoincash:prsgx6z6…t0knqzkespentOutput 1 · OP_RETURN0.00000000 BCHscript f835832b7b…54b7bf0aunspent
Value flow: 1 input to 2 outputsCoinbase 13.24793076 BCH; to Output 0 · P2SH 13.24793076 BCH; Output 1 · OP_RETURN 0.00000000 BCH;in 0out 0out 1

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

Settlement check

Input total

Coinbase

no inputs spent; new coins plus fees

Output total

13.24793076

BCH, 2 outputs

Miner fee

None

a coinbase pays no fee

Fee rate

—

not applicable

Size

204 B

version 1, locktime 0

CashTokens

None

no token prefix on any output

Coinbase: it creates 13.24793076 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/BTC.COM/mm11!,=31?+_rK5…”

Unlocking script · 74 bytes

<0xc22d07>
<0xb22f3a59>
<0x4254432e434f4d2ffabe6d6d3131ab02f9212c3dc83331aea09deed73f1d2b5f92b072b0af4ba48ec435a1d8010000>
<0>
<0>
<0>
<0>
<0>
OP_TXVERSION
<0xe5>
UNKNOWN_OPCODE
OP_OUTPOINTTXHASH
03c22d0704b22f3a592f4254432e434f4d2ffabe6d6d3131ab02f9212c3dc83331aea09deed73f1d2b5f92b072b0af4ba48ec435a1d80100000000000000c201e5f0c80e000000000000

Outputs2 · 13.24793076 BCH

Spend states looked up for 2 of 2 outputs: 1 spent, 1 unspent.
#AddressTypeSpentAmountScripts
0prsgx6z6…t0knqzke
P2SH
Spent13.24793076 BCH
Scripts

Spent byca791e971766dd448cdd2d51f88530a75e56e82d5472387c538fbdde94d33d78 input #12 in block 470,594

Locking script23-byte pay-to-script-hash output (20-byte hash)

Locking script bytes · 23 bytes

OP_HASH160
<0xe083685a1097ce1ea9e91987ab9e94eae33d8a13>
OP_EQUAL
a914e083685a1097ce1ea9e91987ab9e94eae33d8a1387
1script f835832b7b…54b7bf0a
OP_RETURN
Unspent0.00000000 BCH
Scripts

Locking scriptMetadata output: “$!~}\[~fTx.6UjBe”

Locking script bytes · 38 bytes

OP_RETURN
<0xaa21a9ed7eca8b7deea25cac5bd7f77e661d54078b78c1b92e3655dea994056af0de4265>
6a24aa21a9ed7eca8b7deea25cac5bd7f77e661d54078b78c1b92e3655dea994056af0de4265
Position in block 470,466Open 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
470,466
Byte offset in block
83
Block hash
00000000000000000004a13db48c2e76ad5fba30dcefca2168f00f02954f912a
Merkle proof

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

01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4a03c22d0704b22f3a592f4254432e434f4d2ffabe6d6d3131ab02f9212c3dc83331aea09deed73f1d2b5f92b072b0af4ba48ec435a1d80100000000000000c201e5f0c80e000000000000ffffffff02f4bcf64e0000000017a914e083685a1097ce1ea9e91987ab9e94eae33d8a138700…5bd7f77e661d54078b78c1b92e3655dea994056af0de426500000000
Show full hex
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4a03c22d0704b22f3a592f4254432e434f4d2ffabe6d6d3131ab02f9212c3dc83331aea09deed73f1d2b5f92b072b0af4ba48ec435a1d80100000000000000c201e5f0c80e000000000000ffffffff02f4bcf64e0000000017a914e083685a1097ce1ea9e91987ab9e94eae33d8a13870000000000000000266a24aa21a9ed7eca8b7deea25cac5bd7f77e661d54078b78c1b92e3655dea994056af0de426500000000
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...