Mainnet

Configured chains

Coinbase transaction · Bitcoin Cash Mainnet

Confirmed transaction

0d0f0d8e30d2a7bfc1536d4002df5347b46fccb8eeae18f60ce0d647fa87f305

Status

Confirmed499,893 confirmations

Included in

block 475,239 · 2017-07-11 04:52:13 UTC · 9 yr ago

Previous blockNext blockBlock list

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

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

Settlement check

Input total

Coinbase

no inputs spent; new coins plus fees

Output total

13.58189293

BCH, 2 outputs

Miner fee

None

a coinbase pays no fee

Fee rate

—

not applicable

Size

208 B

version 1, locktime 0

CashTokens

None

no token prefix on any output

Coinbase: it creates 13.58189293 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: “g@wYdY/BTC.COM/NYA/mm ?>@Q6N3 65DV!NI\Bs…”

Unlocking script · 78 bytes

<0x674007>
<0x77596459>
<0x4254432e434f4d2f4e59412ffabe6d6d097f3fb8ba3e1ec84051364eecbdcb33d8dd20df36ff35449056214e495cd0>
OP_1SUB
<0x00>
<0>
<0>
<0>
<0>
<0>
<0>
OP_CHECKSIG
0367400704775964592f4254432e434f4d2f4e59412ffabe6d6d097f3fb8ba3e1ec84051364eecbdcb33d8dd20df36ff35449056214e495cd08c0100000000000000ac42b873edca71dc00000000

Outputs2 · 13.58189293 BCH

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

Spent bya2b11f012c01737aa1445bfac04ccfb99e3368e8077fef0746a2d68fa07d051c input #2 in block 475,719

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

Locking script bytes · 23 bytes

OP_HASH160
<0xe083685a1097ce1ea9e91987ab9e94eae33d8a13>
OP_EQUAL
a914e083685a1097ce1ea9e91987ab9e94eae33d8a1387
1script 119b5c80b8…110995d3
OP_RETURN
Unspent0.00000000 BCH
Scripts

Locking scriptMetadata output: “$!N~]e-A7Hk`I”

Locking script bytes · 38 bytes

OP_RETURN
<0xaa21a9edd24e7e8b0604a55d1a65a4f82d41871ed3d5a5cb1ad59e3718ec486bfb6049c9>
6a24aa21a9edd24e7e8b0604a55d1a65a4f82d41871ed3d5a5cb1ad59e3718ec486bfb6049c9
Position in block 475,239Open 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
475,239
Byte offset in block
83
Block hash
0000000000000000007eafd6101e8be7fbc1582dd236b71be1744e6bbaca1214
Merkle proof

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

01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4e0367400704775964592f4254432e434f4d2f4e59412ffabe6d6d097f3fb8ba3e1ec84051364eecbdcb33d8dd20df36ff35449056214e495cd08c0100000000000000ac42b873edca71dc00000000ffffffff02ed52f4500000000017a914e083685a1097ce1ea9e91987ab9e94eae33d…1a65a4f82d41871ed3d5a5cb1ad59e3718ec486bfb6049c900000000
Show full hex
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff4e0367400704775964592f4254432e434f4d2f4e59412ffabe6d6d097f3fb8ba3e1ec84051364eecbdcb33d8dd20df36ff35449056214e495cd08c0100000000000000ac42b873edca71dc00000000ffffffff02ed52f4500000000017a914e083685a1097ce1ea9e91987ab9e94eae33d8a13870000000000000000266a24aa21a9edd24e7e8b0604a55d1a65a4f82d41871ed3d5a5cb1ad59e3718ec486bfb6049c900000000
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...