Quantus mainnet · Transaction-pool desk · 100% client-side
Read the pool before the block does
Connect to any Quantus node and watch its transaction pool in real time: pending-extrinsic gauges, live txWatch signals the second a transfer requests your address, and node-quoted fee estimates on what's actually waiting. No node, no data — nothing here is ever simulated.
Connect a node
Any Substrate WebSocket RPC works — your own node, or the upstream-documented public mainnet RPC. The endpoint is saved in this browser only.
Socket status
Session log
Reconnects use exponential backoff (1s → 30s cap) and resubscribe every watcher automatically. Upstream notes the txWatch RPC is unauthenticated — operators exposing it publicly should front it with a reverse proxy or rate limits; if your node's pool RPCs are gated, the desk tells you exactly which calls the node refused instead of guessing.
Pending extrinsics from author_pendingExtrinsics, newest poll
⚠ Zero-confirmation signals — read this first
- A signal means a transaction requesting a transfer to your address entered the node's pool with a valid signature. It does not mean the transfer happened, or ever will.
- The transaction may be dropped, replaced, or fail at execution — and anyone can craft a convincing-looking signal that never moves funds.
- Never release goods, mark an invoice paid, or credit a balance on a signal alone. Confirm inclusion in a finalized block first (per the upstream txWatch docs).
Watch an address
SS58 addresses on prefix 189 are checksum-validated before they join. One txWatch subscription per address covers every payment to it.
Watched addresses
Pool signals unconfirmed transfer requests, newest first
How fee quotes work here
Every quote below comes from the connected node's payment_queryInfo — the same partialFee the runtime would charge at the current head. The desk never invents a fee. Amounts are shown in QTC (1 QTC = 1012 planck, per upstream docs).
Quote a single extrinsic
Paste any signed extrinsic hex (0x…) and the desk asks your node what it would cost.
Why the pool matters on Quantus
Quantus transactions are large — post-quantum ML-DSA signatures push a typical transfer toward ~7 KB — and the chain handles that with native transaction aggregation (claimed ~430 TPS design throughput). A fat mempool is where fee pressure shows up first: this desk reads it raw.
Size/throughput figures are Quantus's stated design claims (Sept 2026 coverage); the pool gauges above measure the live reality instead.
txWatch — the pool-listener RPC
A Quantus node addition (chain/docs/rpc_additions/transaction_pool_listener.md), built for point-of-sale payment detection:
txWatch_watchAddress(address)→ subscription idtxWatch_transfernotifications:{tx_hash, from, amount, asset_id}txWatch_unwatchAddress(subscriptionId)to release- Watches native transfers, asset transfers, and
batch_allnests up to 4 deep - Error 5011 = invalid SS58 address
The 5-step receive flow (per upstream)
- Generate the invoice — QR with your address + expected amount.
- Open the txWatch subscription for that address.
- Wait for the signal — show “payment detected, confirming…”.
- Verify execution — wait for a finalized block and check the
Balances.Transferevent or the balance. - Unsubscribe when the payment screen closes.
Node-operator notes
- Reconnect with backoff — WebSockets drop; this desk does.
- txWatch has no per-method cap, but nodes bound it at
--rpc-max-connections(100) /--rpc-max-subscriptions-per-connection(1024). - Batch payments fire one notification per matching transfer inside the same
tx_hash— call data, not execution outcome. - Only port 30333 (P2P) is meant to be public; keep RPC 9944 and the miner port private or proxied.
Data honesty
This desk has no demo mode and no fallback dataset. Every number on screen came from the socket you connected, in the last few seconds — or the desk says plainly that it has no data. If your node gates author_pendingExtrinsics, the Mempool tab says so instead of inventing a pool.