QRL transactions are XMSS-signed instructions on the Quantum Resistant Ledger mainnet, a Proof-of-Work chain preparing its migration to QRL 2.0. This feed lists the newest confirmed transactions, each with its hash, type, sender, recipient(s), value and fee, newest first. The filters show every transaction, only what people sent, or only the block rewards (coinbase) paid to miners.
What each column means: status, type, the amount sent and the fee.
Show the full column guideHide column guide
Status
Check = accepted by the protocol; cross = rejected but still recorded on chain.
Transaction ID
The transaction's unique hash. Click to open its detail page, including any multi-recipient breakdown.
Method
The QRL transaction subtype: transfer, token, message or slave (delegate signing). EVM smart-contract calls don't exist on QRL.
Block
Block height that confirmed this transaction.
Age
Time since confirmation. Hover for the exact UTC timestamp.
From / To
Sender and recipient(s). A single QRL transfer can pay several recipients at once: the detail page lists each destination.
Amount
Native value transferred, in Quanta. For multi-recipient transactions this is the total across all recipients; the detail page breaks it down.
Fee
Fee chosen by the sender to encourage inclusion. There is no base-fee market: miners simply prefer higher-fee transactions.
FAQ about transactions
Common questions about this page+
How is the original QRL chain different from QRL 2.0?
The original QRL chain is a Proof-of-Work network that launched in 2018, signed with XMSS hash-based signatures. QRL 2.0 is its next-generation successor: an EVM-compatible Proof-of-Stake chain using ML-DSA-87 (lattice-based) signatures with full smart-contract support. The QRL community is transitioning to QRL 2.0; this page shows transactions on the original Proof-of-Work chain.
How long does a QRL transaction take to confirm?
A QRL transaction is confirmed once a miner includes it in a block — typically within a minute or two given the 60-second target block time. Because Proof-of-Work has no protocol-level finality, it's conventional to wait for several additional blocks (6-12) before treating a transaction as settled. For everyday transfers one or two confirmations is usually enough.
What types of QRL transactions exist?
QRL has a fixed set of native transaction subtypes: transfer (move QRL), transfer_token (move a token), token (create a new token), message (publish text on-chain), slave (delegate signing authority), lattice (register post-quantum lattice keys), multisig (create / spend / vote on a multi-signature wallet), and governance proposal (create / vote). Block rewards appear as a coinbase subtype: the protocol pays one to the miner of every block. The filters above the table show every transaction, only the ones people sent (without block rewards), only block rewards, or a single subtype, each with its count. The Method column tells you which subtype each row uses. EVM-style smart-contract calls don't exist on the PoW chain — those are a QRL 2.0 smart-contract feature.
What is a multi-recipient transaction on QRL?
QRL supports paying multiple recipients in a single signed transaction — a feature most chains do not offer natively. The sender lists each destination and amount; the protocol applies all transfers atomically and the sender pays one fee. The detail page shows every recipient and their slice; the listing here groups by transaction hash and shows the total moved across all recipients.
How is the QRL transaction fee determined?
The sender picks the fee when they sign the transaction. 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 what the sender chose to pay.
Why can each XMSS address only sign a limited number of transactions?
XMSS is a hash-based, one-time-signature scheme: each address holds a finite tree of one-time signing keys (typically 2¹⁰ to 2²⁰ leaves, depending on the address type), and re-using a leaf compromises the address's security. Wallets track how many signatures you've used and warn you when you're near the limit. Generating a new address gives you a fresh tree.
What is a 'master address' on QRL?
QRL supports a delegation pattern: a master XMSS address can authorise one or more slave addresses to sign on its behalf. The slave address signs the transaction, but the chain records the master as the authoritative owner. This lets long-running services rotate signing keys without changing their identity. The Master column on the transaction-detail page surfaces this relationship when it applies.
What makes QRL transactions quantum-resistant?
Every QRL transaction is signed with XMSS — the eXtended Merkle Signature Scheme — standardised by NIST in 2020 (SP 800-208). XMSS is built on cryptographic hash functions rather than the discrete-log or factoring problems that Shor's algorithm breaks on a quantum computer, so its signatures are expected to remain unforgeable even against an attacker with quantum hardware.
What's the relationship between the original QRL chain and QRL 2.0?
They are distinct chains with a predecessor/successor relationship. The original QRL chain is the Proof-of-Work network that launched in 2018; QRL 2.0 is its next-generation Proof-of-Stake successor, with smart-contract support and newer post-quantum cryptography. The QRL community is transitioning to QRL 2.0 — tokens on each chain are tracked as distinct assets, so check the project's official documentation for the current state of migration and any bridging tools.