Skip to content
CryptoAcademy logo CryptoAcademy
Menu
Lesson Beginner · 15 min

Transactions

A transaction is a signed statement: "move these inputs to these outputs". No account numbers, no balances — just cryptographic proof of authorisation.

In this lesson

  • Break a transaction into inputs, outputs and signatures
  • Explain UTXO and account models
  • Follow the broadcast-to-confirmation journey

A signed statement

The life of a transaction
A transaction is signed, broadcast, verified, included in a block and then confirmed 1 Sign Owner proves ownership with their private key 2 Broadcast Sent to peers and flooded across the network 3 Verify Every node checks signature, inputs and double-spending 4 tx Include A miner/validator puts it in a candidate block 5 Confirm Each new block on top adds one confirmation Why every step matters Without a signature (1) anyone could spend your coins; without verification (3) invalid transactions would enter the ledger. Wallets usually wait for 6 confirmations (~1 hour on Bitcoin) before considering large payments final.
Signed in your wallet, gossiped through the mempool, packaged into a block, then confirmed by depth.

Every node validates a transaction the same way: 1) every input carries a valid signature from its owner, 2) the inputs exist and are unspent, 3) inputs ≥ outputs (the difference is fee/change), 4) no double-spend already in the chain. No identity check, no reversal button.

UTXO model (Bitcoin)
  • Transactions spend unspent outputs like cash notes
  • Parallel-friendly, simple double-spend check
  • Privacy is better by default
Account model (Ethereum)
  • Transactions debit/credit balances like a bank ledger
  • Smart-contract friendly, stateful
  • Easier balances, harder history hygiene

Example · Paying a café

You scan a QR code; your wallet builds a transaction spending a 0.015 BTC output you received earlier, sending 0.01 to the café and 0.0049 back to yourself as change, paying 0.0001 in fee. Signed with your key, gossiped, and picked up by a miner within seconds.

tx.json json
{\n  "inputs": [{ "txid": "9f2b...", "vout": 0, "scriptSig": "3045...0221..." }],\n  "outputs": [\n    { "value": 0.01000000, "address": "bc1q..." },\n    { "value": 0.00490000, "address": "bc1qm... (change)" }\n  ]\n}

Fees are the market

Fees compete for block space: when demand spikes, users attach higher fees and miners prioritise them. This is the mechanism that keeps spam expensive.

Transactions are final by design

There is no chargeback. Sending to the wrong address, signing a malicious contract approval, or falling for address-poisoning malware all result in permanent loss. Verify the first and last characters of addresses — or use hardware-wallet verification.

Sign and broadcast

Build a transaction in the lab, sign it, then corrupt the signature and watch every node reject it.

Try it yourself
How fast is confirmation?

First inclusion is typically seconds to a minute; "safe" depth depends on the network and the value at stake.

Can transactions be censored?

Individual transactions can be delayed by fee pressure or miner policy; protocol-level censorship resistance is a decentralisation metric, not a guarantee.

What reveals my identity?

The chain never sees names — but exchanges, reuse of addresses and off-chain metadata can deanonymise you.

Share this page

Send this link to a friend, or scan the QR code to open it on your phone.