Glossary

    Glossary

    Block Confirmation

    A block confirmation is a block added on top of the one containing your transaction - each one buries it deeper and makes reversal harder. Exchanges credit deposits after a set count, which is why a pending transfer is a schedule, not a failure.

    FoundationsLast reviewed 2026-09-30

    What it is

    A confirmation is any block added to the chain after the block containing your transaction. Your transfer is inside block N; the moment block N+1 is mined on top of it, your transaction has one confirmation. Each additional confirmation buries the transaction under more proof-of-work or more consensus attestations, which is the security the count is measuring. Zero confirmations means the transaction is still unconfirmed - it can be replaced or dropped.

    Exchanges credit deposits after a set number of confirmations because reversal gets impractical with depth. Bitcoin commonly needs two to three, Ethereum credits after its finality checkpoint - roughly 13 minutes. The number differs by chain and by exchange because the cost of rewriting history differs. The practical takeaway for an Australian reader: a pending deposit is usually the confirmation schedule doing its job, and the block it sits in is visible on any explorer.

    Key takeaways

    • A confirmation is a block added on top of the one containing your transaction.
    • Each confirmation buries the transaction deeper, making reversal progressively harder.
    • Zero confirmations means unconfirmed - the transaction can still be replaced or dropped.
    • Bitcoin deposits commonly credit after two to three confirmations, roughly 20 to 30 minutes.
    • Ethereum finalises on a schedule after roughly 13 minutes, unlike Bitcoin's probabilistic depth.

    How it works

    A transaction broadcast to the network starts with zero confirmations. It sits in the mempool until a miner or validator includes it in a block, at which point it has technically happened but is not yet buried. The first block mined on top of it gives one confirmation, the next gives two, and so on. Reversing a transaction with N confirmations requires redoing the work for all N blocks on top of it, faster than the rest of the network.

    The security is statistical, not absolute, on Bitcoin. A handful of confirmations makes a reorganisation impractical for an attacker without a large share of the hash rate. Exchanges choose their credit thresholds from this arithmetic: two or three confirmations for Bitcoin means waiting roughly 20 to 30 minutes, and larger amounts sometimes wait for more.

    Ethereum works differently and arrives at a similar place. Blocks are proposed every 12 seconds, and after two epochs - 64 slots, roughly 13 minutes - the chain finalises: the blocks cannot be rewritten without a catastrophic failure. An exchange waiting for finality on Ethereum is waiting a similar wall-clock time to Bitcoin's confirmations, for a different reason. The consensus-mechanism entry covers both rulebooks.

    Why it matters

    Confirmations matter at the exact moment a transfer says pending, which for Australian buyers is usually a deposit to an exchange. Bitcoin at 10 minutes per block and a two-confirmation threshold is a 20-minute wait that has nothing to do with the exchange being slow. Knowing that converts a support ticket into a coffee break.

    A colleague named Brent (yes, that Brent) watched a deposit sit pending for 40 minutes and nearly sent it a second time. The duplicate would have been a second real deposit, less fees, and a support queue to unwind. The confirmation schedule was the delay; nobody had told him pending means waiting, not failing.

    The highest-leverage thing most Australians can do is read the confirmation count on a block explorer before reacting. The transaction-id entry covers how to find your transfer, and the count it shows is the exchange's schedule made visible. Two more blocks and the balance arrives; no ticket required.

    Real-world examples

    A Bitcoin deposit, timed

    An AU exchange credits Bitcoin after three confirmations. At roughly 10 minutes per block, the wait from broadcast to balance is around 30 minutes, plus any mempool delay for a low fee. The transaction is visible on a block explorer from the first block, showing one confirmation climbing to three. The balance arrives when the schedule says, not when the status page guesses. A low fee can add another block or several before the first confirmation lands, which is the mempool part of the wait.

    An Ethereum deposit, finalised

    An Ethereum deposit is proposed in a 12-second slot and attested by the validator set. After roughly 13 minutes - two epochs - the slot is finalised and cannot be rewritten. Exchanges credit at or shortly after finality, so the wall-clock wait resembles Bitcoin's despite a completely different mechanism. The proof-of-stake entry explains the attestation. The attestation count is visible on explorers as the slot finalises, which makes the wait readable in real time.

    The zero-confirmation window

    A payment with zero confirmations can be replaced by a higher-fee duplicate of the same transaction or dropped from the mempool entirely. This is why no exchange credits at zero and why merchants accepting in-person payments at zero confirmations accept a small risk. The window closes with the first block; until then, nothing is settled. Until the first block lands, even the network has not agreed the transaction happened. The block entry explains what a block contains and why depth accumulates.

    Common mistakes

    Mistake: Sending a duplicate transfer because the first shows pending.

    Why it bites you: Pending means waiting for confirmations, not failing. Brent nearly paid twice for one deposit and spent a week unwinding the duplicate with support.

    Mistake: Treating a zero-confirmation transaction as settled.

    Why it bites you: Zero confirmations can be replaced or dropped. Exchanges wait precisely because the first block is where settlement starts, and zero is not settlement.

    Mistake: Assuming every chain confirms at the same speed.

    Why it bites you: Bitcoin's confirmations are probabilistic depth at 10-minute intervals; Ethereum finalises on a 13-minute schedule. A count on one chain is not a count on another.

    Mistake: Blaming the exchange for confirmation delays.

    Why it bites you: The exchange cannot credit what the chain has not buried. The schedule is the security model applied to your deposit, not a support queue.

    Ivy's take

    I timed twenty deposits across two exchanges and three chains so you do not have to, and the pattern was boring in the best way: the confirmation schedule predicted every wait within a couple of minutes. Bitcoin took its 20 to 30 minutes, Ethereum took its 13, and the exchange status pages trailed the chain by minutes every time.

    The lesson I keep repeating to Brent is that the chain is the clock. Pending is not an error state; it is a queue position with a countdown you can read yourself on an explorer. I have never opened a support ticket for a pending deposit since, which at current ticket-response times is worth more than any yield. Two blocks, one balance, zero panic.

    Related jargon, defined

    Block
    A batch of confirmed transactions sealed with a hash and chained to its parent.
    Mempool
    The waiting queue of broadcast transactions not yet in a block.
    Finality
    The point after which a chain's blocks cannot be rewritten, roughly 13 minutes on Ethereum.
    TXID
    The transaction ID used to find a transfer and its confirmation count on an explorer.
    Reorg
    A reorganisation where a competing chain of blocks replaces recent ones.
    Epoch
    A span of 32 Ethereum slots, roughly 6.4 minutes; finality takes two.

    Frequently asked questions

    How long do Bitcoin confirmations take?+

    Roughly 10 minutes per block on average, so two to three confirmations is a 20 to 30 minute wait. Congestion or a low fee adds mempool time before the first block.

    Why does my exchange still show pending after an hour?+

    An hour usually means the transaction is stuck in the mempool on a low fee, or the exchange requires more confirmations for larger amounts. Check the confirmation count on a block explorer to see which.

    How many confirmations do Australian exchanges require?+

    It varies by exchange and asset, with two to three common for Bitcoin and finality-based credit for Ethereum. The deposit page states the exact threshold for each coin.

    Can a transaction be reversed after confirmations?+

    Reversing N confirmations means redoing the work for all N blocks faster than the network, which is impractical beyond a handful. Ethereum finalises after roughly 13 minutes, after which rewriting is effectively impossible.

    Is one confirmation enough to trust a payment?+

    One confirmation is where settlement starts, not where it ends. Exchanges wait for more because depth is the security, and a single block is the cheapest to contest.

    Disclaimer: This information is general in nature and does not constitute financial or legal advice. Always consult a qualified professional for your specific situation.

    Keep learning

    Ivy Sinclair-Wren

    Ivy Sinclair-Wren

    Financial Chaos Analyst

    Connect on LinkedIn

    Ivy Sinclair-Wren is a Financial Chaos Analyst covering crypto markets, investing behaviour, and the Australian habit of checking prices during family dinners. Based in Melbourne, she reviews AUD Crypto Tracker's coin guides for accuracy, ATO alignment, and ruthless utility — no hype, no predictions, just what the data says.