Skip to content
QuantascanAlpha

Blocks and transactions

What a transaction is, what a block is, and how they fit together — the two core objects you'll see all over this explorer.

5 min readUpdated 2026-06-20

On this page

Two objects show up everywhere on this explorer: transactions and blocks. Understanding them makes every other page easier to read.

Transactions: the instructions

A transaction is a signed instruction submitted to the network. The most common kind says "move this much value from this address to that one," but transactions can also create tokens, deploy a contract, or call one.

Every transaction is signed by the sender's private key. On QRL that signature is quantum-resistant — XMSS on Legacy, ML-DSA-87 on QRL 2.0 — which is how the network proves the sender really authorised it without ever seeing the private key itself. A transaction typically carries:

  • a from and to address,
  • an amount,
  • a fee (paid to the block producer), and
  • a hash — its unique fingerprint, which you can paste into search.

Blocks: the batches

The network doesn't confirm transactions one by one; it groups them into blocks. A block bundles many transactions and adds:

  • a height — its sequential position in the chain (block #1, #2, …),
  • a timestamp,
  • the hash of the previous block (the link that forms the chain), and
  • who produced it (a miner on QRL Legacy, a validator on QRL 2.0).

New blocks arrive at a roughly regular cadence. On QRL 2.0, that cadence is anchored to 60-second slots.

Confirmations and finality

When your transaction lands in a block, it has one confirmation. Each new block built on top adds another. Because rewriting a block means redoing every block after it, more confirmations means the transaction is harder to reverse — effectively permanent once it's deep enough. QRL 2.0's Proof-of-Stake design also adds an explicit notion of finality through the beacon chain.

What's different between the two chains

  • QRL Legacy transactions are a fixed set of types (transfers, the mining reward, token and message operations). One transfer can pay multiple recipients at once.
  • QRL 2.0 transactions are EVM-style: simple transfers, plus contract creations and calls, with fees metered in gas. Validator rewards arrive as separate protocol withdrawals, not as ordinary transactions.

Where to go next

FAQ about Blocks and transactions

Common questions about this page
What is a blockchain transaction?
A transaction is a signed instruction to move value or run a contract — for example, 'send 10 from address A to address B'. It is signed by the sender's private key so the network can verify it's authentic, then included in a block.
What is a block?
A block is a batch of transactions confirmed together, stamped with a time, a height (its position in the chain) and a hash of the previous block. Blocks are produced at a regular rhythm by miners (QRL Legacy) or validators (QRL 2.0).
What is a confirmation?
A confirmation is a block built on top of the one containing your transaction. The more blocks stacked on top, the harder it becomes to reverse — so more confirmations means more certainty the transaction is final.