Bitcoin Confirmations Explained: What They Mean for a Solo Block Find

Bitcoin Confirmations Explained: What They Mean for a Solo Block Find

"Unconfirmed", "1 confirmation", "6 confirmations", "immature" — block explorers and wallets throw these words around as if everyone already knows what they mean. For a solo miner they matter more than for almost anyone else, because if your Bitaxe ever finds a block, the reward in that block goes through its own, much longer confirmation wait before it can be spent. Knowing how that works turns a nervous refresh-the-explorer moment into something you can read calmly.

A confirmation is a count of blocks. A transaction has one confirmation when it is included in a block, and gains one more with every block built on top of that one. Each new block makes the earlier ones harder to reverse, because changing an old block would mean redoing its proof of work and all the work after it. Waiting for six confirmations is a common convention, not a protocol rule. The coinbase transaction — the one that pays a block finder — has a stricter, consensus-enforced rule: its outputs cannot be spent until they have 100 confirmations. On Bitmern Solo, keep BTC easy-start host btc.bitmernsolo.com with port :3132 (never treat :3102 as the Bitaxe / home default), username WALLET.worker, password x. Current Effort is not a find guarantee.

This is the "what happens after a block is found" lane. If you want what the finder's reward transaction is, read the coinbase transaction explained. If you want what happens when two blocks compete, read orphaned (stale) blocks explained. This post connects the two.

Bitmern Solo is solo infrastructure: flat 1% fee on finds only, you keep 99%. Nothing in this post is financial advice, and nothing here promises a find.

The one-sentence version

A confirmation is one more block stacked on top of yours, and every block on the stack makes yours harder to undo.

What "unconfirmed" means

When someone sends bitcoin, their transaction is broadcast to the network and sits in node mempools until a miner includes it in a block. While it waits, it is unconfirmed: valid, visible, but not yet part of the blockchain. Read the mempool and transaction fees explained for how transactions get picked.

An unconfirmed transaction can still be replaced or, in some cases, never be included. That is why careful recipients wait.

How confirmations are counted

Count it like a stack:

1. Included in a block → 1 confirmation.
2. One more block on top → 2 confirmations.
3. Each later block → one more.

So confirmations equal the current chain height, minus the height of the block containing the transaction, plus one. The network targets roughly 10 minutes per block on average, but the gap between any two blocks varies a lot. Sometimes several blocks arrive in minutes; sometimes one takes much longer. Confirmations count blocks, not minutes. The difficulty adjustment is what keeps the long-run average near the target.

Why more confirmations means more certainty

Nodes follow the valid chain with the most cumulative proof of work. A block near the tip can occasionally be replaced if a competing block at the same height wins out — that is a stale (often called orphaned) block. The deeper a block is, the more work an alternative chain would have to redo to replace it, and the less likely that becomes.

Practically:

• 0 confirmations: still in mempools; not in a block yet.
• 1 confirmation: in a block, but near the tip, where short competitions can still happen.
• A few confirmations: much harder to reverse.
• Many confirmations: treated as settled by nearly everyone.

There is no single moment where a block becomes "100% final". Certainty grows with every block.

Why "6 confirmations" is a convention

You will see six confirmations quoted everywhere. It is a widely used rule of thumb for larger payments, not something the protocol enforces. Exchanges, merchants, and wallets each choose their own threshold based on how much risk they accept. If someone tells you a payment is "confirmed", ask how many confirmations they mean.

The special rule for block rewards: 100 confirmations

The coinbase transaction is different from every other transaction. It does not spend earlier coins; it creates new ones (the subsidy) and collects the fees of the block's transactions. Because that reward would simply not exist if the block were replaced, Bitcoin's consensus rules require coinbase outputs to wait until they have 100 confirmations before they can be spent.

That is coinbase maturity. Explorers and wallets often label the reward immature until it gets there.

Why it matters for solo miners:

• If your Bitaxe finds a block, the reward appears on the blockchain immediately, in that block's coinbase.
• It cannot be moved until it matures.
• If, during the early confirmations, your block were replaced by a competing block at the same height, its coinbase would not exist on the winning chain. Maturity exists so that rewards are only spendable once that risk is effectively gone.

Read what happens when you find a block for the full sequence, and payout timing for how timing works on Bitmern Solo.

How to read confirmations on an explorer

1. Find the block. Use the block height or hash shown in the Blocks / finds dashboard.
2. Open the coinbase transaction. It is the first transaction in the block.
3. Read the confirmation count. Most explorers show it next to the transaction or block.
4. Check maturity. Under 100 confirmations, the coinbase is still immature.
5. Check the output address. In solo mining the payout relates to the wallet in your WALLET.worker username, per the pool's payout rules.

For a full walkthrough, read verify a payout on an explorer.

A worked timeline (EXAMPLE values only)

EXAMPLE ONLY — placeholder heights, not a real block
height N        your Bitaxe's hash beats the network target -> block N found
                coinbase in block N: subsidy + fees -> 1 confirmation (immature)
height N+1      next block built on N -> 2 confirmations
height N+5      6 confirmations -> common "settled" convention for payments
height N+99     100 confirmations -> coinbase maturity reached
after that      reward spendable / handled per pool payout rules

Ordered "confirmations and my solo setup" checklist

1. Confirm the stratum fields

Symptom: You want to be sure a find would be credited to you.

Fix: In AxeOS, check the stratum settings. Host:

btc.bitmernsolo.com

Port:

3132

Username:

WALLET.worker

Password:

x

Never treat :3102 as the Bitaxe / home default.

2. Make sure the wallet part is correct

Symptom: You are not sure which address would be paid.

Fix: The wallet part of the username is where a find is credited. To change it, follow change payout wallet.

3. Turn on alerts

Symptom: You do not want to miss a find while away.

Fix: Set up email alerts so you hear about it instead of checking by hand.

4. Do not panic at "immature"

Symptom: You found a block and the explorer says the reward is immature.

Fix: That is expected for the first 100 confirmations. It is the protocol, not a problem with your miner.

5. Do not panic at a rare replacement

Symptom: A very recent block disappeared from an explorer.

Fix: Short competitions at the chain tip happen occasionally. Read orphaned (stale) blocks explained.

6. Read Current Effort correctly

Symptom: Current Effort is high and you expect a find soon.

Fix: Current Effort is not a find guarantee — read Current Effort explained. Solo results are lumpy; see solo mining variance.

What this post will not invent

• No probabilities of a block being replaced at a given depth
• No Bitmern Solo payout-processing timelines beyond what its own docs state
• No price, profitability, or ROI figures — no financial advice
• No claim that :3102 is the home Bitaxe default (easy-start is :3132)

Common confirmation misunderstandings

1. "One confirmation means 10 minutes." Confirmations count blocks; block intervals vary.
2. "Six confirmations is a Bitcoin rule." It is a convention. Each service picks its own threshold.
3. "Immature means my reward is stuck." It means the 100-confirmation coinbase maturity rule is still running.
4. "Confirmations can go down." Normally they only go up. They can reset only if a block is replaced near the tip, which is uncommon.
5. "More hashrate makes confirmations faster." Your miner does not speed up the network's block rate.
6. "High Current Effort means a block is coming." It does not. Current Effort is not a find guarantee.

Soft next step

Open AxeOS and confirm the stratum fields above, with the wallet you want paid in WALLET.worker. Turn on alerts, then open the matching coin tab on Bitmern Solo and watch accepted shares arrive. If one of your hashes ever wins, you now know exactly what the confirmation count is telling you. Keep BTC easy-start btc.bitmernsolo.com with port :3132 and password x.

Start mining

Start Mining — after login, open the matching coin tab and confirm workers / shares / hashrate.

FAQ

What is a Bitcoin confirmation?

A count of blocks. One confirmation when a transaction is included in a block, plus one for each block added after it.

How many confirmations are enough?

There is no protocol rule for ordinary payments. Six is a common convention; services set their own thresholds.

Why does a mined block reward need 100 confirmations?

Bitcoin's consensus rules make coinbase outputs unspendable until they have 100 confirmations, so rewards only become spendable once the block is deep in the chain.

What does "immature" mean on an explorer?

The coinbase reward has not reached 100 confirmations yet.

Does the Bitmern Solo fee change with confirmations?

No. It is a flat 1% fee on finds only — you keep 99%.

Does Current Effort mean I am about to find a block?

No. Current Effort is an ops / attribution signal — not a find guarantee. See Current Effort explained.