Mainnet

Coinbase transaction · Bitcoin Cash Mainnet

Confirmed transaction

5ce30bdb3a8b685875d4070a7a392fe906ff7bd2d7d2c02eeb792daf4ddadff6

Status

ConfirmedAt least 1 confirmation

Included in

block 960,916 · 2026-07-23 19:40:23 UTC · 3 mo ago

Previous blockNext blockBlock list

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

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

Settlement check

Input total

Coinbase

no inputs spent; new coins plus fees

Output total

3.12656903

BCH, 2 outputs

Miner fee

None

a coinbase pays no fee

Fee rate

—

not applicable

Size

233 B

version 1, locktime 0

CashTokens

None

no token prefix on any output

Coinbase: it creates 3.12656903 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: “/ViaBTC/Mined by bakande0098/,mm%a-r["tV…”

Unlocking script · 96 bytes

<0x94a90e>
<0x2f5669614254432f4d696e65642062792062616b616e6465303039382f>
<0xfabe6d6dc88425e861fbfcf22d72e49b1d5be32287c774d9562c5d7a27c1987a83d279ff1000000000000000>
<0x44bf810c31b37d91cab2da94b0010000>
0394a90e1d2f5669614254432f4d696e65642062792062616b616e6465303039382f2cfabe6d6dc88425e861fbfcf22d72e49b1d5be32287c774d9562c5d7a27c1987a83d279ff10000000000000001044bf810c31b37d91cab2da94b0010000

Outputs2 · 3.12656903 BCH

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

Spent by642ef4d0516ff1b80ac8bfed12b3b392db568fd5ea53424b9037164dfa35e2de input #2 in block 961,036

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 06ecfa6991…90a9fb09
OP_RETURN
Unspent0.00000000 BCH
Scripts

Locking scriptMetadata output: “)RSKBLOCK:^D9<eZ\{2YAiz5…”

Locking script bytes · 43 bytes

OP_RETURN
<0x52534b424c4f434b3a5e448739cf90873c65ab175a5c7bc6e5933206598641c5d169157a0f008a9e35>
6a2952534b424c4f434b3a5e448739cf90873c65ab175a5c7bc6e5933206598641c5d169157a0f008a9e35
Position in block 960,916Open 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
960,916
Byte offset in block
81
Merkle proof

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

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

Raw transaction233 bytes

01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff600394a90e1d2f5669614254432f4d696e65642062792062616b616e6465303039382f2cfabe6d6dc88425e861fbfcf22d72e49b1d5be32287c774d9562c5d7a27c1987a83d279ff10000000000000001044bf810c31b37d91cab2da94b0010000ffffffff0207c4a212000000001976a9…65ab175a5c7bc6e5933206598641c5d169157a0f008a9e3500000000
Show full hex
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff600394a90e1d2f5669614254432f4d696e65642062792062616b616e6465303039382f2cfabe6d6dc88425e861fbfcf22d72e49b1d5be32287c774d9562c5d7a27c1987a83d279ff10000000000000001044bf810c31b37d91cab2da94b0010000ffffffff0207c4a212000000001976a914f1c075a01882ae0972f95d3a4177c86c852b7d9188ac00000000000000002b6a2952534b424c4f434b3a5e448739cf90873c65ab175a5c7bc6e5933206598641c5d169157a0f008a9e3500000000

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)
Show scenario JSON
Loading payload...