What is a slave-key authorisation?

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.

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

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.

How is the fee on a QRL transaction determined?

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.

Will the contents of this transaction ever change?

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.

Where does this data come from?

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—Block—

—

QuantascanAlphaBlock Explorer & Analytics

QRL Transaction db1ab1…0797 — Success | Quantascan

QRL Transactiondb1ab15be9e075ff1aef137cb02148b5f897714ff59980f90579076532fd0797

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

Single transaction on QRL — the Quantum Resistant Ledger's Proof-of-Work chain, transitioning to QRL 2.0. Action, sender, recipients, value flow and fee below.

Action

Authorised a slave key

Vibrant RedpollQ01030…60c02 recipients (see breakdown below)

Confirmed in block #3,893,175position #179mo ago2025-11-10 23:11:50 UTC392,772 confssettled

Slave-key authorisation

The master XMSS key delegated signing rights to one or more slave public keys. This is QRL's Proof-of-Work-chain approach to long-lived multi-sig + key rotation.

Slave public keys

#10103007ba419417f9f7817751fb96b686828a58b9f314a308d1e39736b3f52553e5ffc23e354c984a5a49c8f073466079d210448aaf2e48e9880886b6ad2a4fcb34cecaccess 0
#2010300a7d35221efb785ade540b472bfe564ec65733aba7c6c604a6002b92cc571e9f0554cfa9fff7684b88ff94e3e14e66e14f5beed379648f6dc5ad2ddae94c6126eaccess 0
#3010300f98655756721b8b344e9daf15b850f2ddd7aaecf01854515f9c0e71cefc91f445b0058fd0f5f802a022ad3328c8bfe7aea662c78d76d310911ba18b1ec57fd98access 0
#4010300f3e68cd514262d3859e2d2387592cd8117d9771fb052ccd570f41a98c5af8b373a68bbc31b7f343809d5e26f9812dd9574fc0fae8abf9748501ac5885c99b9b9access 0
#5010300c5d92861f65cd5893a2a158298ca321cd2d3a767205a8442078c755153d8643d141d9aac0075c470267cd9dd11a70f734bbc3911c94269eef4472623c9a3c862access 0
#6

More details — hashes & internals

Transaction hash: db1ab15be9e075ff1aef137cb02148b5f897714ff59980f90579076532fd0797
Block hash: 0bf12398af84593ee82cc89bdf75f6832d228f2bc91d0d3e2aff690900000000
Subtype: slave

FAQ about this transaction

Common questions about this page

What is a slave-key authorisation?: 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.
How can I tell if this QRL transaction is fully settled?: 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.
How is the fee on a QRL transaction determined?: 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.
Will the contents of this transaction ever change?: 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.