LEARN ME ABTCMobick
#—
KO

Read a transaction — take apart one that just landed

Fetch a real transaction from a recent Mobick block and unfold its inputs, outputs, fee and locking scripts — the UTXOs and signatures from the basics track, as they are actually written.

8 min Checked 2026.10.08 3 sources Not yet mined
  1. 01
  2. 02
  3. 03
  4. 04
  5. 05
  6. 06
  7. 07

A transaction is a small packet of data

A transaction has four parts:

  • Version — which rules to read it by.
  • Inputs — the UTXOs being spent. Each gives the previous transaction’s ID and output index, plus the signature and public key that unlock it.
  • Outputs — the new UTXOs. Each holds an amount and a locking script stating how it can be spent.
  • Locktime — “do not include before this height (or time).” Usually 0.

The fee is not written anywhere: inputs minus outputs is the fee.

Unfold one that just landed

Below is a real transaction from a recent Mobick block — not a block reward, but a payment between people. Tap inputs and outputs.

Finding a recent transaction…

Inputs — UTXOs spent

    Outputs — new UTXOs

      Tap an input or output to see its script explained.

      FIG. 1Transaction anatomy, fetched live from recent blocks. “Load another” moves to the next.

      Locks and keys

      An output’s locking script is a tiny program. The common 1… address (P2PKH) reads:

      OP_DUP OP_HASH160 <20-byte public-key hash> OP_EQUALVERIFY OP_CHECKSIG

      “Show a public key. Its hash must equal these 20 bytes. Then check the signature with it.” The next transaction’s input supplies the signature and key; nodes run them through the script. If it passes, the UTXO is spent; if anything fails, the whole transaction is refused.

      Read the script — full text
      1. The lock. An output is locked to the receiver's public-key hash. The lock says: bring the public key that hashes to this, and a signature made with it.
      2. The key. When a transaction wants to spend this coin, it shows a signature and the public key. Nodes then check two things, in order. First, does the public key hash to the locked value? Second, checked with that key, does the signature fit this transaction? Both pass, so the coin is spent. If either check fails, the whole transaction is refused.
      3. Predict. Your turn to predict. Someone shows the right public key, but a signature copied from an older, different transaction. What happens? Answer: it is refused. The first check passes, but the signature is bound to the original transaction, so the second check fails. So the whole transaction is refused, and the coin stays locked.
      4. So. Without the private key, nobody can spend this coin. Every node checks every transaction this way.

      The narration is synthesized speech.

      bc1q… addresses (P2WPKH) do the same but carry the signature and key in the input’s separate witness. Witness data is weighted less, so the same transaction has a smaller virtual size (vB) and pays less — why the transaction box shows both bytes and vB.

      Summary

      • Transaction = version + inputs (UTXOs spent, with signatures) + outputs (amounts with locking scripts) + locktime.
      • A locking script is a small program saying “only the owner of this key hash may spend.”
      • Fee = inputs − outputs; miners choose by fee rate (sat/vB).

      Check yourself

      Get them right to add a block to your chain

      1. Q1What does a transaction input contain?

      2. Q2What does a P2PKH locking script require?

      Sources

      1. Mobick mempool explorer API (blockchain.mobick.info)
      2. Bitcoin Developer Guide · Transactions
      3. BIP-141 · Segregated Witness

      Found a mistake or a policy that changed? Tell us by email →