What does 'registered post-quantum keys' mean?

This transaction registers a set of lattice-based public keys on chain — typically Kyber for encryption and Dilithium for signatures, alongside a legacy ECDSA key. Registering them on chain lets counterparties look up the keys before encrypting messages or verifying signatures, all anchored to the registering XMSS address.

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 ec577f…1abc — Success | Quantascan

QRL Transactionec577f00a8c3b3e426b51cd06e50b26a585866f7cd9bb4d4264cd11f8d4e1abc

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

Registered post-quantum keys

Fancy BadgerQ00050…86aa—

Confirmed in block #1,061,009position #16y ago2020-06-28 08:24:28 UTC3,225,482 confssettled

Post-quantum key registration

Lattice-based public keys (Kyber for encryption, Dilithium for signatures, plus a legacy ECDSA key) registered on chain so counterparties can look them up later.

Kyber public key (encryption): 185e20aeff86d3c4a73b025cf9627f19aa29ca8441862fd667312d347b78dd3be4fc46911c482c8a68afaec8143d8312848c8b30880e976edec269615bcb9fd6a4304bd803bb1fa9a37ffd200708173ccb104e0b32b423056e18dbb6b8e993cb42f27272a622da9b7e60f1f7416c9e596fa3bc412ad6e26b4ed381b11c08b7a05c1c40504b8f4c4106ede7c4d067edff8001718a2d7627248ea9ab5f39c9359a3c19cd4880375067f2ca222946872e7ad5dcb6fe9afe63341f193a0806ad466c10b04956fa0f59d543735f351443442c475b8f9a94a6e1777e5c92fe227af06f01422176a16b3f460011bdc14c2809b28fc0f97f65f1f241c91eca56b68d23cb510ce95778ca845e10a44645d7b42f6729676fd271f808de17b5e64731c295a27ee13b4d3ef47eefb17100263498143a4ab9862987c4ae5f69a0a1eab649b16bc9b43ccf8d0f94975f2364aeaf530b477baf40063df87bd3d0427caf100b47941d2c6eedd02878cec50932a91fd01a0bc9ad68b203b71b756e988cfc221c9384e52a6d22f3f5147a7d04ef5ceff06b34af57ed435ee8c388fa1effb611851275f0e1e22eee1f16e3e56490b4a21c28dbd6e24697f9f00c6ea002190ce723a3498f1e8600ec27bc08d9125475da82b18c42ad08b80d9e876b6aa013c3947a948c2de3925ec1a386432b6fd9f0913e1e1e6a3f534ea7926770877006743dfcab3723cd8c94687c0edf0dee9ecfbfead4b75055ac75a41c8218f1ddaf56f5db038137feae646161d735130229af269a730864b2cfb6a45caf337aaee5a81e1f138fd0f8a37901cedd9ad7ee2bfab7d555aea9526bfa3082b8a9a11448a7b19c066f44058f1af11ab80db2743b68960e5f04b30ccc8cc1a087ec79abe873b7bde7a5739ad81941167075c7a4ddfc6b30c3e3a211ee7c2ce4412ecfe096888998dd63836f56d77f2616d2826bd09a295440efa56d15f755833fcdc7fa1b005b0a4d9f0c7b557d679f7be2994f72142abc0b6c60f37ff5e2c9ced9961271f887495383e9f47ccca14d8236fe6f2ea8411cde623472402bb7bf8851d0d6817665982d132cb6d43976feab7801905459d023a5c91307f82dc368dfe1706ddbde6efb8c0d0432bf6ab0c87f04191a83481fefa1f2f020af72d3d17ba09f4534487271b97f66dbc7222e974478a7642723c1a2418b4342ea6537d829901f7b6ffb4e6aebcb40cd63156ab0e61be9288a0c4b4bd3436125720ad8b19135c0c622f23b12c353d7459273517736e1ef45fd51b17b9ac8d5fe4ac17521b5107f65fbd39f0e20a450dc7cc766dbd9df02e2fe649b8d5276909d7030e128b3c2e76046132a4bf21be010052a662fdf8d6461cfd8a745bfd931c3a15ef6698790e25d8cc9ca796d45b3d92a046f0bce7e77ed36fa37231c66437d0ac296306bc22e943218ce93ab1424f3ed5a100b4494d5570e3ba72c567e46ef1e31a5dd5ac93e1eddbecc215847dbc5bd29c18536235347ede25fa5519d67d5cb2c7b7258a5ea3e73f586b39c9e
Dilithium public key (signatures)

More details — hashes & internals

Transaction hash: ec577f00a8c3b3e426b51cd06e50b26a585866f7cd9bb4d4264cd11f8d4e1abc
Block hash: e9c42badc4c439c6c115c4a5eb15567481e246f111d46aa5deb5206b01000000
Subtype: lattice_pk

FAQ about this transaction

Common questions about this page

What does 'registered post-quantum keys' mean?: This transaction registers a set of lattice-based public keys on chain — typically Kyber for encryption and Dilithium for signatures, alongside a legacy ECDSA key. Registering them on chain lets counterparties look up the keys before encrypting messages or verifying signatures, all anchored to the registering XMSS address.
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?

Action

Registered post-quantum keys

Fancy BadgerQ00050…86aa—

Confirmed in block #1,061,009position #16y ago2020-06-28 08:24:28 UTC3,225,482 confssettled

Post-quantum key registration

Lattice-based public keys (Kyber for encryption, Dilithium for signatures, plus a legacy ECDSA key) registered on chain so counterparties can look them up later.

Kyber public key (encryption): 185e20aeff86d3c4a73b025cf9627f19aa29ca8441862fd667312d347b78dd3be4fc46911c482c8a68afaec8143d8312848c8b30880e976edec269615bcb9fd6a4304bd803bb1fa9a37ffd200708173ccb104e0b32b423056e18dbb6b8e993cb42f27272a622da9b7e60f1f7416c9e596fa3bc412ad6e26b4ed381b11c08b7a05c1c40504b8f4c4106ede7c4d067edff8001718a2d7627248ea9ab5f39c9359a3c19cd4880375067f2ca222946872e7ad5dcb6fe9afe63341f193a0806ad466c10b04956fa0f59d543735f351443442c475b8f9a94a6e1777e5c92fe227af06f01422176a16b3f460011bdc14c2809b28fc0f97f65f1f241c91eca56b68d23cb510ce95778ca845e10a44645d7b42f6729676fd271f808de17b5e64731c295a27ee13b4d3ef47eefb17100263498143a4ab9862987c4ae5f69a0a1eab649b16bc9b43ccf8d0f94975f2364aeaf530b477baf40063df87bd3d0427caf100b47941d2c6eedd02878cec50932a91fd01a0bc9ad68b203b71b756e988cfc221c9384e52a6d22f3f5147a7d04ef5ceff06b34af57ed435ee8c388fa1effb611851275f0e1e22eee1f16e3e56490b4a21c28dbd6e24697f9f00c6ea002190ce723a3498f1e8600ec27bc08d9125475da82b18c42ad08b80d9e876b6aa013c3947a948c2de3925ec1a386432b6fd9f0913e1e1e6a3f534ea7926770877006743dfcab3723cd8c94687c0edf0dee9ecfbfead4b75055ac75a41c8218f1ddaf56f5db038137feae646161d735130229af269a730864b2cfb6a45caf337aaee5a81e1f138fd0f8a37901cedd9ad7ee2bfab7d555aea9526bfa3082b8a9a11448a7b19c066f44058f1af11ab80db2743b68960e5f04b30ccc8cc1a087ec79abe873b7bde7a5739ad81941167075c7a4ddfc6b30c3e3a211ee7c2ce4412ecfe096888998dd63836f56d77f2616d2826bd09a295440efa56d15f755833fcdc7fa1b005b0a4d9f0c7b557d679f7be2994f72142abc0b6c60f37ff5e2c9ced9961271f887495383e9f47ccca14d8236fe6f2ea8411cde623472402bb7bf8851d0d6817665982d132cb6d43976feab7801905459d023a5c91307f82dc368dfe1706ddbde6efb8c0d0432bf6ab0c87f04191a83481fefa1f2f020af72d3d17ba09f4534487271b97f66dbc7222e974478a7642723c1a2418b4342ea6537d829901f7b6ffb4e6aebcb40cd63156ab0e61be9288a0c4b4bd3436125720ad8b19135c0c622f23b12c353d7459273517736e1ef45fd51b17b9ac8d5fe4ac17521b5107f65fbd39f0e20a450dc7cc766dbd9df02e2fe649b8d5276909d7030e128b3c2e76046132a4bf21be010052a662fdf8d6461cfd8a745bfd931c3a15ef6698790e25d8cc9ca796d45b3d92a046f0bce7e77ed36fa37231c66437d0ac296306bc22e943218ce93ab1424f3ed5a100b4494d5570e3ba72c567e46ef1e31a5dd5ac93e1eddbecc215847dbc5bd29c18536235347ede25fa5519d67d5cb2c7b7258a5ea3e73f586b39c9e
Dilithium public key (signatures)

More details — hashes & internals

Transaction hash: ec577f00a8c3b3e426b51cd06e50b26a585866f7cd9bb4d4264cd11f8d4e1abc
Block hash: e9c42badc4c439c6c115c4a5eb15567481e246f111d46aa5deb5206b01000000
Subtype: lattice_pk

FAQ about this transaction

Common questions about this page

What does 'registered post-quantum keys' mean?: This transaction registers a set of lattice-based public keys on chain — typically Kyber for encryption and Dilithium for signatures, alongside a legacy ECDSA key. Registering them on chain lets counterparties look up the keys before encrypting messages or verifying signatures, all anchored to the registering XMSS address.
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?

8caf7b4dc41d541f78a58b678ed6d11f6d7daffb5fec0da14ff1027301f4fcb87da8ec8a61f31cbe6749e5bf1df614116da772b7615b91a9f9d7cd87c2b90f2701efe6e8cc82deb2af9550e8e3fedab36560fea5765abbb0a93007f2a77cc2ecec15c39045f8484a7c25f144973e4ea62f97607ad2538945372d91a8e34d27dc5dc707d856e228609d702f5cbe53ee38841fbd9ccf8fe69aa092fcbd7384cecc0cb969b81bf7d39e30d9c4f6741c32473a828f32644b3dab6483cb748bcf8c89c708da1990e6b610fae8624748181289cd288d5d451a14a65af4287e02e8beb8e0d809f30c49f0dc7e5a710847f190ec807eed21adefbb6bb260cf9a74bd2a4d46851b2e047a046fb303d83a96eb94a190d65dbd7359145c6ac756037a9fecc1040b3a5ae683771d46c1993c7e870fb689746b0eddeb99880945125cf78346ea620250f1cd79270944ac4c2aeee11224b4c6daada491e4ee0be79e7aee66aca7816ab04dd51df297c76d26a5e3243038c72093014a24356f571cb123eee5bdacdbab82022a57436aa000dca0765c6d0e268c35195a54dea0f9891c9ca9a06583a8ec0df948cc9d13ebe9cc6d675271626a465cb379b1c24caae0ee3eba670fcd64088a36aa7ddf4b4150eb39835c2a33eae6d0b80e1ccb75746cc68038a551b611f8f303f156889373ec06fa11fba5856cb0b93fd54c40166bf8fce9bb8d6028625281eb37490f570274fc83ed33e14fb7394210a28403c29fc3a63b1728ea24f6021e47171f0a8706f8b0e34cd5c6130a81e5726e9390e729d07888dc629b845c1c7111066b43d232f8709819bfe58159133b95c83b76ade54a7a57b6f4eec452034f1141b8aaaf0ce45ed98ac266d6ea6d4c2bb222e1d76b903cb0a40b38d3a5a48d6d35410f714666f5eefe92a0abf1a01d69e1649b0a25fabde2b0554d4dfe72a94a9d412e59825d907194128171c807a9a90165672508884aa712664a686d98dfed4d4f65085fb98560cd42211dba7e2765cd1015d830866c7db9f478ac736c334fc6aaea76b69816e8c5175a3a6de29c317aaa7cbebcadd8a052464b336964cbf78a25d05da9675305006865f2948da08815baafa46a4598b57c1fe4340ccc028aedc4a5ff29a9835f284ca88ee4c2d300c10b79ee97d015fe7f36dcee14f72299d4f00f524fb6ea2c67f495a16117a623d6e08194d3486d520aa6e1815c8a90877649bb572687cca976c0664d8b237e902016d2b5579c0dc784ad523c4b27c4d186447e004dfec43d152f12b8671cd1604b57872abd899d3923cefcbd6467997f61330841b3beba23b41ce4204c78152b3e3cbfb19446771d334772a27aab0835b246d07a2921d69cc5902f2c441432258eac19494352003191924597df06e1fddcbb57080be06d8556f7ad592e68b21fbee00ce6acdba5a41d01bc67050e8c365fcb561eb8cd2b6423356a7ff97c204b450425bbd541635075d9401971aede251afd49ac8e311b1aa984931e1c8eae36f3835c3285485186772310ad12a008bcd0bb76f6f4793144cdbc32f3de894875bfe7ed84d60bf182b5f84f202855012224487623489874d386a8e73746931a69707a778148eb48f8aecec83710cee62f54a58d46fc571252e26ebbbd2540e515815e15d6991444c2adb295646c66f97dd91e18e4b1a1dedf3e7b8a2d8e2744cb677702f3ca002bacba57e9764f93cfb7c74ac050371d4b91fd1df7b1d7abcaa41dabf4b4c4c56d0d7d431e0396b2749170afe8bcb84a21f875e1fa0c2596ef320caf2eca7b51a1285321e630335d3d4f77dbf7f9c0392f623699fef1579b0c50c16aa8e434e4536367371be598a50dc7f8e69cca8efcf984e990022ea3dc4ad473dd4d885a1185ac7a2e13732f075afd40d3839cde30366a2fa3af2e7892fdf24de95bbf7f6a74c348f5d4a0d46033877e395ab404099aec34a2d73d900760a80e72552203912df323a3db3effa0dfd51b353f0e3b8b75f2ae592142b2053ab0e483364f1ea286bdad079dc0e42a5e44f9f04829eb8b977877daffe7a0c64adc10adb9573662b9282dc6f702