Mainnet

Coinbase transaction · Bitcoin Cash Mainnet

Confirmed transaction

b68cf071b76a951eead52bf82fc56ac8aed5a2c025d2aa5e635c048fc4b2a68e

Status

Confirmed58,910 confirmations

Included in

block 914,542 · 2025-09-03 15:39:29 UTC · 13 mo ago

Previous blockNext blockBlock list

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

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

Settlement check

Input total

Coinbase

no inputs spent; new coins plus fees

Output total

3.13200294

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.13200294 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: “n /ViaBTC/Mined by farshid1405/,mmNZ(qwD…”

Unlocking script · 96 bytes

<0x6ef40d>
<0x2f5669614254432f4d696e65642062792066617273686964313430352f>
<0xfabe6d6d4e050f0fb05ac32871abf0779a93bdc18d44d7be54658b4e03ace6103bc710d21000000000000000>
<0xfaaff401afa3692a7d697110bb550100>
036ef40d1d2f5669614254432f4d696e65642062792066617273686964313430352f2cfabe6d6d4e050f0fb05ac32871abf0779a93bdc18d44d7be54658b4e03ace6103bc710d2100000000000000010faaff401afa3692a7d697110bb550100

Outputs2 · 3.13200294 BCH

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

Spent by519647cd9733708aa35be3d9851bc7a011f15540810cce49c4aed5f76c45c47e input #4 in block 914,659

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 ed22be4452…dc2f8d96
OP_RETURN
Unspent0.00000000 BCH
Scripts

Locking scriptMetadata output: “)RSKBLOCK: & s8"\&vsm nyk/…”

Locking script bytes · 43 bytes

OP_RETURN
<0x52534b424c4f434b3ab40a8f260a7307dba4ab8b93fc38225c182676a4cb8e736d0a966e1600796b2f>
6a2952534b424c4f434b3ab40a8f260a7307dba4ab8b93fc38225c182676a4cb8e736d0a966e1600796b2f
Position in block 914,542Open 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
914,542
Byte offset in block
81
Merkle proof

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

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

Raw transaction233 bytes

01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff60036ef40d1d2f5669614254432f4d696e65642062792066617273686964313430352f2cfabe6d6d4e050f0fb05ac32871abf0779a93bdc18d44d7be54658b4e03ace6103bc710d2100000000000000010faaff401afa3692a7d697110bb550100ffffffff02a60eab12000000001976a9…a4ab8b93fc38225c182676a4cb8e736d0a966e1600796b2f00000000
Show full hex
01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff60036ef40d1d2f5669614254432f4d696e65642062792066617273686964313430352f2cfabe6d6d4e050f0fb05ac32871abf0779a93bdc18d44d7be54658b4e03ace6103bc710d2100000000000000010faaff401afa3692a7d697110bb550100ffffffff02a60eab12000000001976a914f1c075a01882ae0972f95d3a4177c86c852b7d9188ac00000000000000002b6a2952534b424c4f434b3ab40a8f260a7307dba4ab8b93fc38225c182676a4cb8e736d0a966e1600796b2f00000000

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...