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

Question 1

What is a slave-key authorisation?

Accepted Answer

QRL lets a master XMSS address delegate signing rights to one or more 'slave' public keys. The slave can sign transactions on the master's behalf, with optional access flags constraining what it's allowed to do. This is QRL's approach to long-lived multi-sig + key rotation — useful when the master's XMSS one-time-signature tree is being conserved for high-value operations.

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 Transaction91fce371310d219fa5e751a35154b70378e10ff3cc3d8ffe8b3c7c57d139c5c6

Authorised a slave key

Slave-key authorisation

FAQ about this transaction

Authorised a slave key

Slave-key authorisation

FAQ about this transaction