Mainnet

Configured chains

Coinbase transaction · Bitcoin Cash Mainnet

Confirmed transaction

d4e58e02bda749c1d8f95a21553c238fb615ea280ccf250f5c834a4e39a98cbb

Status

Confirmed96,863 confirmations

Included in

block 877,236 · 2024-12-19 09:47:47 UTC · 22 mo ago

Previous blockNext blockBlock list

Value flowRibbon height is proportional to value.
Value flow: 1 input to 2 outputsCoinbase 3.13180121 BCH; to Output 0 · P2PKH 3.13180121 BCH; Output 1 · OP_RETURN 0.00000000 BCH;100.0% of input valueCoinbase3.13180121 BCHnew coins plus the block's feesOutput 0 · P2PKH3.13180121 BCHbitcoincash:qrcuqadq…xw4gmv6pspentOutput 1 · OP_RETURN0.00000000 BCHscript b2bcde5a5e…b73357c9unspent
Value flow: 1 input to 2 outputsCoinbase 3.13180121 BCH; to Output 0 · P2PKH 3.13180121 BCH; Output 1 · OP_RETURN 0.00000000 BCH;in 0out 0out 1

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

Settlement check

Input total

Coinbase

no inputs spent; new coins plus fees

Output total

3.13180121

BCH, 2 outputs

Miner fee

None

a coinbase pays no fee

Fee rate

—

not applicable

Size

217 B

version 1, locktime 0

CashTokens

None

no token prefix on any output

Coinbase: it creates 3.13180121 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: “b /ViaBTC/BCHN/,mmILQPHNg:s|yu,,Zww/…”

Unlocking script · 80 bytes

<0xb4620d>
<0x2f5669614254432f4243484e2f>
<0xfabe6d6d494c06be51501c48ba968e4e673ac273eafd7c79f0c6752cf8fcda2ceb5a77bf1000000000000000>
<0xd17fc800fee61385779d8bab2fe7b800>
03b4620d0d2f5669614254432f4243484e2f2cfabe6d6d494c06be51501c48ba968e4e673ac273eafd7c79f0c6752cf8fcda2ceb5a77bf100000000000000010d17fc800fee61385779d8bab2fe7b800

Outputs2 · 3.13180121 BCH

Spend states looked up for 2 of 2 outputs: 1 spent, 1 unspent.
#AddressTypeSpentAmountScripts
0qrcuqadq…xw4gmv6p
P2PKH
Spent3.13180121 BCH
Scripts

Spent bydb833a9b8913722c716e118876d1e763acff13cd55935bbd4855e83d2526e991 input #4 in block 877,366

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

Locking script bytes · 25 bytes

OP_DUP
OP_HASH160
<0xf1c075a01882ae0972f95d3a4177c86c852b7d91>
OP_EQUALVERIFY
OP_CHECKSIG
76a914f1c075a01882ae0972f95d3a4177c86c852b7d9188ac
1script b2bcde5a5e…b73357c9
OP_RETURN
Unspent0.00000000 BCH
Scripts

Locking scriptMetadata output: “)RSKBLOCK:1p5FJtdkY…”

Locking script bytes · 43 bytes

OP_RETURN
<0x52534b424c4f434b3accea317019c4979ac6f0b335b04617cde34a82e574c364cc0c19d207006b598a>
6a2952534b424c4f434b3accea317019c4979ac6f0b335b04617cde34a82e574c364cc0c19d207006b598a
Position in block 877,236Open 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
877,236
Byte offset in block
83
Block hash
000000000000000000e0b88ab08fed8450be530d271b3eea82974c4c6daa8332
Merkle proof

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

01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff5003b4620d0d2f5669614254432f4243484e2f2cfabe6d6d494c06be51501c48ba968e4e673ac273eafd7c79f0c6752cf8fcda2ceb5a77bf100000000000000010d17fc800fee61385779d8bab2fe7b800ffffffff02d9bfaa12000000001976a914f1c075a01882ae0972f95d3a4177c8…c6f0b335b04617cde34a82e574c364cc0c19d207006b598a00000000
Show full hex
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff5003b4620d0d2f5669614254432f4243484e2f2cfabe6d6d494c06be51501c48ba968e4e673ac273eafd7c79f0c6752cf8fcda2ceb5a77bf100000000000000010d17fc800fee61385779d8bab2fe7b800ffffffff02d9bfaa12000000001976a914f1c075a01882ae0972f95d3a4177c86c852b7d9188ac00000000000000002b6a2952534b424c4f434b3accea317019c4979ac6f0b335b04617cde34a82e574c364cc0c19d207006b598a00000000
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...