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

Question 1

Why does this transaction pay multiple recipients?

Accepted Answer

QRL supports paying multiple recipients in a single signed transaction — a feature most chains don't offer natively. The sender lists each destination address and amount; the protocol applies all transfers atomically, and the sender pays one fee for the whole envelope. The Transfer diagram above breaks out exactly what each recipient received.

Question 2

Did each recipient get the same amount?

Accepted Answer

Not necessarily — the sender chooses an amount per recipient when signing. Each recipient is listed in the Transfer diagram above with exactly what they received. The transaction's Amount field is the sum across all recipients; the listing on /transactions collapses these into one logical row per transaction hash.

Question 3

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 4

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 5

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 6

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 Transaction7a3a95c3dc91602439779d365fc2acbb2a4d46e29fb3a5c15f88cc294b895bd7

Sent 50 Quanta to 2 wallets

Transfer

FAQ about this transaction

Sent 50 Quanta to 2 wallets

Transfer

FAQ about this transaction

Attached message