- What is the mempool, and what does 'pending' mean?
- The mempool ('memory pool') is the network's waiting room. When a wallet broadcasts a QRL 2.0 transaction, every node it reaches relays it via peer-to-peer gossip and holds a copy in its local mempool until the next validator picks it up for inclusion in a block. A pending transaction is one that nodes have seen and accepted as valid but that has not yet landed in a block. Each node keeps its own view of the mempool; this page reflects what our node observes.
- Why doesn't the original Proof-of-Work QRL chain show pending transactions?
- The QRL 2.0 client (gqrl) exposes its mempool over the qrl JSON-RPC namespace, which lets external services subscribe to pending-transaction notifications via qrl_subscribe(newPendingTransactions). The legacy QRL node maintains an internal mempool too, but does not expose it publicly — there is no data feed for us to index, so the /qrl-legacy/pending page is unavailable by design.
- Why does a transaction sometimes disappear from this list?
- Three reasons. Confirmed — the transaction landed in a block and now appears on the regular transactions feed. Replaced — the sender broadcast a new transaction with the same nonce and a higher priority fee, evicting the original. Pruned — it sat pending too long without being picked up (low fee, mempool full) and the node dropped it from its local view.
- Can I cancel or speed up a pending QRL 2.0 transaction?
- Yes. Broadcast a replacement transaction from the same sender, using the same nonce as the one you want to override, and offer a higher priority fee. To cancel, send a zero-value transfer to yourself; to speed up, re-send the original action with a higher tip. Most wallets expose both as one-click actions. Once a transaction is included in a block it cannot be replaced.
- Why might my transaction be stuck pending?
- The two most common reasons are a fee that's too low (the base fee has risen since you broadcast and your max-fee-per-gas is now under the floor — miners and validators ignore it) or a missing earlier nonce (nonce 5 hasn't landed yet, so nonces 6+ from the same sender wait in the mempool until 5 confirms or is replaced). Replace-by-fee with a higher tip is the standard fix.
- Why is there no Fee or Status column on this page?
- Pending transactions don't have a receipt yet, so there's no success/fail status and no realised fee — those only exist after a block has executed the transaction. The sender's signed gas limit and max fee are visible on the transaction-detail page, but the actual fee paid (gas used × effective gas price) cannot be known until execution. Once the transaction confirms it appears on the regular transactions page with its full fee and status.
- What is the 'Sequence #' column?
- It's the transaction's nonce — a strictly-increasing per-account counter. The network executes transactions in nonce order, so if nonce 5 is still pending, the network will not execute nonce 6 from the same sender. The Sequence # column lets you trace one sender's mempool ordering at a glance.
- Is a pending transaction the same as a failed one?
- No. Pending means the transaction is valid and waiting in the mempool to be included in a block — it hasn't executed yet, so it has no success-or-fail status. A transaction only succeeds or reverts after a block runs it; until then it is simply unconfirmed, and most pending transactions confirm within seconds.
- How does this feed work, and how fresh is the data?
- Quantascan subscribes to qrl_subscribe(newPendingTransactions) on our own QRL 2.0 archive node over the gqrl WebSocket port. Every time the node sees a new pending transaction, our subscriber fetches the full transaction body via qrl_getTransactionByHash and persists it for up to one hour. The view automatically hides transactions that have already landed in a block, and the table on this page polls our backend every 10 seconds — end-to-end, a new broadcast typically appears here within 10-20 seconds of reaching our node.
- How long does a pending QRL 2.0 transaction take to confirm?
- Usually the next block. QRL 2.0 produces one block every 60-second slot, so a transaction with the correct next nonce and a tip at or above the current base fee is typically picked up by the next proposer — confirming within roughly a minute. It waits longer only when an earlier nonce from the same sender is still pending, or when its max-fee-per-gas has dropped below the base fee. Full finality (two epochs, ~4h 16min) comes later; first inclusion is what clears it from this list.