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—

—

QuantascanAlphaAlphaBlock Explorer & Analytics

QRL Transaction94e53d5104c8f1cd23164dcfdf5eaaf0a185fd8a912b076b51f291d58e80ce76

Name: QRL (PoW) Transaction 94e53d5104…
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.

Official explorer

QRL Transaction94e53d5104c8f1cd23164dcfdf5eaaf0a185fd8a912b076b51f291d58e80ce76

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.

Official explorer

Action

Authorised a slave key

Canny Paddlefish7c966Q01030…eecb—

Confirmed in block #2,994,189position #32y ago2024-02-26 06:29:55 UTC1,393,038 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

#101030061e0bab3463d788983ac666d95e8b03b69b8102a560fea8c0ce3d8148c511a45dbfae6d001c388ec49bd3009ad436f3eab3bda5a3bb3c65db7f44de92acafe18access 0
#2010300787e44bb5a73040ebc22804dd6cb8be49d6f83b4d5f59ce0e4e5da8293bbf73803d8de54727740c5b1070b88e07e27f3385fcdbf80d50adce3573ed90d3ae04caccess 0
#30103007254731a48a68d62d4e2deb3bff0cf60ca5bdf38bd7e22c2383ea3e65d1e8ba3e0566ff99fdad5dec5ef4abd2a08e782589a807cc384d638f1cc5f4d0072c36daccess 0
#4010300a963995055053491b9b30592b7c9c6a47c57e9dec88d3b38a251c2f9f3c6e616f3300813434d4a1d1342614fdb4721ea911112e872ffabf880b5f83277d70b8caccess 0
#5010300b786cc6ba8616c43c106b1815eac945c3f3a999ff3814145d66f9f48a8a030327931b87173bc755b0c422fa939690293d20930fd06a2ca543bd1b76130bcd05caccess 0
#6

More details — hashes & internals

Transaction hash: 94e53d5104c8f1cd23164dcfdf5eaaf0a185fd8a912b076b51f291d58e80ce76
Block hash: a642fed30b07b7325dbb9a2507067e78501f911dd5e680ec030b53ca08000000
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.