Name: QRL (PoW) Transaction dc660bc4be…
Creator: Quantascan
License: https://creativecommons.org/publicdomain/zero/1.0/

Question 1

What is a coinbase transaction?

Accepted Answer

A coinbase transaction is how the protocol pays the miner who produced this block. There is no real signer — the QRL is newly minted by the protocol — and the To address is the miner who solved the Proof-of-Work puzzle. The Amount is the block reward: a static portion (which decreases over time per the emission curve) plus the sum of every fee from the block's other transactions.

Question 2

How can I tell if this QRL transaction is fully settled?

Accepted Answer

QRL uses Proof-of-Work with cumulative-work resolution rather than protocol-level finality. The conventional rule of thumb is to wait 6-12 block confirmations on top of the confirming block before treating a transaction as fully settled. Click the block link in the action header to navigate to the confirming block, then use Prev/Next to check how many blocks have accumulated on top.

Question 3

How is the fee on a QRL transaction determined?

Accepted Answer

QRL fees are sender-set: when signing, the sender picks the fee they want to attach. There is no EIP-1559 base-fee market — miners are free to pick whichever transactions they want from the mempool, but in practice they prioritise higher-fee transactions. The Fee column shows exactly what the sender chose to pay; the miner of the confirming block received the full fee.

Question 4

Will the contents of this transaction ever change?

Accepted Answer

No. Once a transaction has accumulated enough confirmations its contents are effectively permanent — rewriting it would require redoing all the Proof-of-Work for every block on top, which is computationally infeasible. The XMSS signature is also unforgeable under classical and quantum threat models, so the transaction's authorship and content are anchored to history forever.

Question 5

Where does this data come from?

Accepted Answer

Quantascan indexes from a QRL archive node we operate ourselves — no third-party API in the pipeline. The transaction body comes from QRL's gRPC PublicAPI (GetTransactionByHash), with sender-address resolution via GetAddressFromPK and an LRU cache so XMSS-tree roots resolve to their on-chain Q-prefix address consistently.

QRL Transactiondc660bc4bead858736abd178d5ed2f491592393e15a86913686288e7aa2977e8

Mining reward of 1.362753183 Quanta

Transfer

FAQ about this transaction

Mining reward of 1.362753183 Quanta

Transfer

FAQ about this transaction

Coinbase — block reward