Glossary

    Glossary

    Block

    A block is a batch of confirmed transactions sealed with a cryptographic hash and chained to the block before it. Blocks are the ledger's pages - roughly 10 minutes apart on Bitcoin, 12 seconds on Ethereum.

    FoundationsLast reviewed 2026-09-30

    What it is

    A block is a batch of transactions that has been confirmed and permanently added to a blockchain. Each block carries a header - a compact summary containing the previous block's hash, a timestamp, and a fingerprint of every transaction inside called the merkle root. The link to the previous hash is what turns a stack of blocks into a chain. Change one character anywhere in an old block and its hash changes, which changes every hash after it.

    Bitcoin produces a block roughly every 10 minutes, and the winning miner claims 3.125 newly issued bitcoin plus fees. Ethereum produces one every 12 seconds through its validator roster, with no mining race at all. The block schedule is why deposits and withdrawals move on the rhythms they do, and why a transfer that says pending is usually just waiting for the next block. Confirmations are simply the blocks added on top of the one containing your transaction.

    The tamper-evidence is the point of the whole design. Editing a block from last year means redoing the work for it and every block mined since, faster than the entire network, which is the arithmetic that keeps the ledger uneditable. For Australian readers, the practical habit is knowing how to read a block on an explorer rather than trusting an exchange's status page.

    Key takeaways

    • A block is a batch of confirmed transactions sealed with a hash and chained to its parent.
    • Editing one block changes its hash and every hash after it, which is the tamper-evidence.
    • Bitcoin produces a block roughly every 10 minutes; Ethereum produces one every 12 seconds.
    • Confirmations are the blocks added after yours, and exchanges credit deposits after a set number.
    • Your transaction ID is how you find a specific transfer inside a block on an explorer.

    How it works

    Transactions broadcast to the network and wait in a queue called the mempool. On Bitcoin, miners select transactions from that queue - usually the highest fee payers first - and bundle them into a candidate block. The miner hunts for a valid nonce, and the first to find one broadcasts the block to the network. Every other participant verifies the block in microseconds and builds the next candidate on top of it. The reward of 3.125 bitcoin plus fees goes to the winner, and the cycle repeats.

    Ethereum runs the same rhythm on a clock. Time is divided into 12-second slots, and a randomly selected validator proposes the block for each slot while the rest attest that it is valid. There is no mining race and no nonce hunt; the schedule holds because the rules, not the hardware, decide who proposes. This is why Ethereum blocks arrive like clockwork while Bitcoin blocks arrive on average, not on time.

    Confirmations are where the security becomes visible. Each block added on top of yours buries the transaction deeper, and rewriting it means redoing the work for the entire stack above it. Exchanges credit deposits after a set number of confirmations - often two or three for Bitcoin - because a handful of blocks makes a reorganisation impractical. Your transaction ID, the TXID, is the lookup key that finds your transfer inside any block on an explorer.

    Why it matters

    Blocks matter to Australian buyers at the exact moment a transfer says pending. The delay is usually the block schedule, not a broken exchange: Bitcoin needs roughly 10 minutes per block, and an AU exchange waiting for three confirmations is waiting roughly half an hour. 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, opened two support tickets, and nearly sent the transfer a second time. The second transfer would have been a second, real deposit into his own account, less the fees, and a support queue to unwind it. The block schedule was the delay; nobody had told him blocks are not instant.

    The highest-leverage thing most Australians can do is read the block schedule before panicking, then look the transaction up directly. The block explorer entry covers how to read a transaction, and checking a TXID takes the exchange's status page out of the loop. The chain is the source of truth; the status page is a rumour about it.

    Real-world examples

    One Bitcoin block, walked through

    A Bitcoin block contains a couple of thousand transactions, a header, and the miner's reward of 3.125 bitcoin plus fees. The header stores the previous block's hash, so the new block physically points backwards at its parent - the mechanic the proof-of-work entry explains in full. Each transaction inside carries its own TXID, which is the string you paste into an explorer to find it. The block lands roughly every 10 minutes on a schedule the difficulty adjustment defends. Anyone on the network can verify the whole package in microseconds, which is the audit nobody had to request.

    Why a deposit waits for confirmations

    An AU exchange receiving a Bitcoin deposit usually credits it after two or three confirmations. At 10 minutes per block, that is roughly 20 to 30 minutes from broadcast to balance. Each confirmation is one more block the attacker would have to redo to reverse the payment, which is why the wait exists. The delay is the security being applied to your deposit, not the exchange being slow.

    The tamper arithmetic

    Suppose someone wants to edit a transaction inside a block mined three days ago. Changing the transaction changes the block's hash, which invalidates every hash stacked above it, so they must redo the work for three days of blocks. On Bitcoin that means outbidding the entire network's hash rate for long enough to catch up. The cost runs into billions, which is why the ledger has never been edited rather than why it cannot be.

    Common mistakes

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

    Why it bites you: The delay is usually the block schedule, not a failed transaction. Brent nearly paid twice in fees for the privilege of unwinding a duplicate deposit.

    Mistake: Treating a transaction in the mempool as confirmed.

    Why it bites you: An unconfirmed transaction can still be replaced or dropped. Exchanges wait for confirmations precisely because the mempool is a waiting room, not a vault.

    Mistake: Expecting Bitcoin transfers to be instant.

    Why it bites you: Blocks arrive roughly every 10 minutes, and most AU exchanges wait two or three of them. A 30-minute deposit window is the design working, not failing.

    Mistake: Assuming every chain finalises the same way.

    Why it bites you: Bitcoin finalises probabilistically with depth; Ethereum finalises on a schedule after two epochs. A confirmation on one chain is not equivalent to one on another.

    Ivy's take

    I spent a morning reading block headers in an explorer so you do not have to, and the header turned out to be the most honest 80 bytes in finance. It names its parent, fingerprints its contents, and stamps the time - a receipt for the entire network's work. The merkle root is the part I respect most: every transaction in the block summarised into one hash. Change a comma in any of them and the whole header confesses.

    The practical version is simpler than the maths. Blocks are pages, confirmations are the pages glued on top, and the TXID is the page number your transaction lives on. I walked Brent through a TXID lookup after his pending-deposit panic, and the support tickets were cancelled mid-typing. The chain was always the source of truth; the status page was just slower gossip.

    Related jargon, defined

    Block header
    The compact summary carrying the previous hash, timestamp, and merkle root.
    Merkle root
    A single hash summarising every transaction in the block.
    Mempool
    The waiting queue of broadcast transactions not yet in a block.
    Confirmation
    A block added on top of the one containing your transaction.
    TXID
    The transaction ID used to look up a transfer on a block explorer.
    Block time
    The average interval between blocks, roughly 10 minutes on Bitcoin.

    Frequently asked questions

    How long does a Bitcoin block take?+

    Roughly 10 minutes on average, with the difficulty adjustment defending that schedule every 2,016 blocks. Individual blocks arrive early or late; the average holds.

    Why is my deposit still pending after an hour?+

    Most exchanges credit Bitcoin deposits after two or three confirmations, which at 10 minutes per block is a 20 to 30 minute wait. An hour usually means a congested mempool or a low fee.

    How many confirmations do Australian exchanges require?+

    It varies by exchange and by asset, with two to three common for Bitcoin and more for smaller networks. The exchange's deposit page states the exact number for each coin.

    What happens when a block is full?+

    Transactions queue in the mempool and the highest fee payers get picked up first. Low-fee transactions wait for the next block or several, which is why fees spike during busy periods.

    What is actually stored inside a block?+

    A header with the previous block's hash, a timestamp, and a merkle root, plus the transactions themselves. On Bitcoin the header also carries the nonce the miner solved.

    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.