Coinbase Output Audit Example: Check Your Block
Use this coinbase output audit example to inspect a solo-mined Bitcoin block, confirm the reward address, and separate subsidy from fees on-chain yourself.
A coinbase output audit example starts after the rare event: your rig found a valid block. The question is not whether a dashboard says you were paid. The question is whether the coinbase transaction in that block sends the block subsidy and transaction fees to the Bitcoin address you configured.
This is a Bitcoin coinbase transaction, not the exchange named Coinbase. It is the first transaction in every block. It creates the new block subsidy and collects the fees from the transactions included in that block. Its outputs show where that value went.
For a solo miner, this is the final custody check. Read the block. Read the coinbase transaction. Read the output script. If it decodes to your address and the value adds up, the reward is where it should be.
What a Coinbase Output Audit Checks
An audit has three parts. First, confirm that the block was accepted by the Bitcoin network. Second, inspect the coinbase transaction outputs. Third, calculate whether the spendable outputs equal the subsidy plus the fees in that block.
The first part matters because a locally found candidate is not yet a Bitcoin block. A valid block must be accepted into the chain. Once it is, it has a block hash, a height, and a transaction list that any full node can return.
The second part answers the custody question. A coinbase transaction can have more than one output. A miner can split a reward across several addresses. A pool can also construct outputs for itself, its users, or another destination. The audit does not assume what the transaction should look like. It shows what it does.
The third part catches an incomplete reading. Seeing your address in one output is not enough if another spendable output sends part of the reward elsewhere. Sum all spendable outputs. Then compare that total with the allowed reward for that height.
Coinbase Output Audit Example
Assume you mined a block at height H and configured the payout address bc1qexample...miner. Your full node returns the block and identifies transaction zero as the coinbase transaction.
A simplified view might look like this:
coinbase transaction
input: coinbase data
output 0: value = subsidy + total fees
script = witness program for bc1qexample...miner
output 1: value = 0
script = OP_RETURN witness commitment
Output 0 is the result you want to inspect. The amount is the entire spendable reward. The script is a locking condition. Wallet software normally decodes that script into a familiar address, but the script itself is the source record. Check both when possible.
Output 1 is normal in a SegWit block. It is an OP_RETURN witness commitment with zero value. It is not a payment and does not reduce the reward. Do not mistake the presence of a second output for a fee or a payout split.
Now consider a different simplified result:
coinbase transaction
output 0: value = part of subsidy + fees
script = witness program for bc1qexample...miner
output 1: value = remaining amount
script = witness program for another address
output 2: value = 0
script = OP_RETURN witness commitment
That block may be valid, but it is not a whole-reward payment to one address. The audit tells you this without relying on labels such as "paid" or "credited." It also tells you the exact amount and script assigned to each destination.
Read the Transaction at the Byte Level When Needed
Most home miners can begin with a block explorer or their own node's decoded transaction view. Compare the displayed address to the address in your miner configuration. Copy carefully. A single changed character means a different destination.
For a deeper check, inspect the output scriptPubKey. A native SegWit address normally corresponds to a version byte and a witness program. The address is a human encoding of that program. Different software can display the same script differently, but the script bytes in the transaction are fixed.
This distinction matters if a tool cannot decode an unfamiliar output type or if you are auditing a script rather than a standard address. The network enforces the output script. An interface label does not.
Calculate the Reward, Not Just the Payout Address
At a given block height, Bitcoin's subsidy is fixed by consensus. The total reward available to the coinbase transaction is:
block subsidy + total transaction fees
To calculate total fees, add the inputs of every non-coinbase transaction and subtract its outputs. Do that for each transaction in the block. The sum of those differences is the fee total.
total fees = sum of all non-coinbase inputs - sum of all non-coinbase outputs
coinbase reward = subsidy at height H + total fees
Then add the values of the coinbase transaction's spendable outputs. Exclude zero-value witness commitment outputs. If the spendable output total matches the reward, the transaction creates no extra spendable value and leaves no reward value unexplained.
If one output pays your address for the full spendable total, the audit is complete. If several outputs pay addresses you control, the value may still be yours, but it is not the one-address arrangement described here. If any spendable output goes to an address you do not control, identify why before treating the block as a direct payout.
There is one limit worth stating plainly. A coinbase output cannot be spent immediately. Bitcoin requires coinbase outputs to mature for 100 blocks before they can be spent. The output is still visible at block acceptance. Maturity affects when you can spend it, not where the block placed it.
Check the Payout Before a Block Exists
An on-chain audit happens after a block is found. A payout preflight is different. It examines the coinbase transaction a pool would build for your configured address on the current block template.
NexusPool (nexuspool.io) provides Payout Preflight for this purpose. It shows the payment destination and proposed output before your rig finds anything. That does not predict when a block will arrive. Solo mining is a lottery, and network difficulty sets the odds at every pool. It checks the path the reward is intended to take if your valid share becomes a block.
For a home miner, the connection path is short. Configure your Bitcoin address as the username and point the rig at solo.nexuspool.io:3350. The pool accepts Stratum V1 and encrypted Stratum V2 on that port. No account holds the reward because the intended payout is constructed inside the candidate block.
A preflight is not a substitute for the final audit. Block contents can change as new transactions arrive, and the fee total can change with them. The address check should remain stable. After a find, inspect the accepted block itself, its coinbase outputs, and the final output value.
Common Mistakes During an Audit
The most common mistake is checking only the address shown by a mining interface. That proves what the interface displayed, not what Bitcoin accepted. Start from the accepted block and work backward.
Another mistake is treating all coinbase outputs as payments. SegWit witness commitments are expected and usually have zero value. Read both the script and the amount before deciding whether an output is spendable.
A third mistake is expecting the coinbase output to equal the subsidy alone. Transaction fees belong in the coinbase transaction too. A block with transactions can have a spendable reward greater than the subsidy. The amount depends on the transactions actually included in that accepted block.
Finally, do not infer a mining schedule from an audit. An audit verifies a block after it exists. It says nothing about when another one will be found. Lower difficulty means a shorter expected wait, not more value, and an average is not a schedule.
The useful habit is simple: keep the payout address you configured, the accepted block hash, the coinbase transaction ID, and the output index together in your records. Those four pieces let you repeat the check later without trusting a dashboard or a memory.
Trust nothing. Verify the coinbase output that pays your address.