Quantus Explorer at qtcscan.com is a QTC block explorer built by the lux8.net team. It provides searchable blocks, accounts, transfers, mining rewards and vesting schedules for the Quantus mainnet.
This explorer displays public chain data. It never asks for a recovery phrase, private key or wallet password.
Where the data comes from
A collector reads a Quantus mainnet node and publishes static JSON snapshots. The browser reads those snapshots; it does not send RPC requests to the node. Block headers, timestamps, raw extrinsics, decoded events, difficulty and mining payouts come from chain data. Peer counts describe the connected node, not the entire network. The displayed finalized head is the node’s reported finalized head; newer canonical blocks can change before finalization.
Block time, difficulty and estimated hashrate
History starts at genesis. Block intervals use the difference between actual adjacent block timestamps. Home charts use 10-minute averages for 24 hours, hourly averages for 7 days and four-hour averages for 30 days. When less history exists, the axis and caption show the available span. Gaps within indexed history remain blank. Estimated hashrate divides accumulated difficulty by observed elapsed time; it is an estimate, not directly reported miner hashrate.
Rewards and miner identities
Mining payouts come from indexed MinerRewarded events and include fees and rounding. Reward addresses come from those events. The header’s author preimage is shown separately in block details and is not treated as an account address. The Miners summary counts rewarded blocks in the trailing 24 hours; it does not use telemetry sample counts.
Miner names are a heuristic from public telemetry (the first node to report a block) and may be wrong; the reward address is the source of truth. Missing or stale telemetry labels fall back to addresses. Account mining history shows recorded payouts, not the account’s current balance.
Snapshots and refresh cadence
Block snapshots and telemetry names refresh approximately every three seconds. Chart aggregates refresh approximately every 15 seconds. Accounts target a complete sweep every 30 seconds, pinned to one latest block that is not yet final. Vesting refreshes about once a minute at one finalized block. The page shows snapshot timing and warns when data is delayed. Actual collection may take longer if the node is unavailable.
Accounts and transfers
Quantus Accounts ranks the top 100 by free plus reserved balance; all indexed accounts remain searchable. Free balance may be subject to locks or freezes and is not necessarily spendable. Issuance share uses the total on-chain issuance at the snapshot block. Pallet accounts hold protocol funds, not user balances. Issuance shares use TotalIssuance, so displayed shares across accounts can add up to more than 100%.
Account history lists Balances.Transfer, Wormhole.NativeTransferred and MiningRewards.MinerRewarded, newest first, with paired events counted once; it does not separately itemize fees or standalone Balances.Minted, Endowed, Withdraw, Deposit, DustLost and other balance adjustments. ProofVerified aggregates are not separate movements; their recorded NativeTransferred credits are included. A ZK-tree record alone does not identify a private transfer. This is not a complete balance ledger.
Vesting and QTC amounts
Quantus Vesting reads current schedules and the pallet pool balance at the same finalized block. Released amounts are recorded payouts, not an estimate from the pool balance. The timeline shows scheduled unlocks under current schedules: nothing before the cliff, linear accrual from start to end after the cliff, and the full scheduled amount at the end. It does not predict future claims or administrative changes.
QTC uses 12 decimal places and Quantus addresses use SS58 prefix 189. Account, transfer and vesting amounts display four decimals, rounded down, with thousands separators; raw JSON preserves full precision.
QTC supply
Supply figures and methodology documents the circulating rule, every excluded address, freshness checks and plain-number endpoints. These computed figures are not official Quantus project figures.
Inspect the source data
Network snapshot · Accounts snapshot · Vesting snapshot · Transaction index coverage
Block and account detail views link to their raw JSON. The Quantus chain source documents the underlying network software.
Why can balances exceed issued supply?
A private wormhole spend does not debit the sending address’s ordinary balance. Displayed balances are therefore upper bounds and the rich list does not prove current ownership. The difference is measured, not estimated: sum every account’s free plus reserved balance and subtract Balances.TotalIssuance at the same latest block. Public nullifiers cannot be linked to the inputs they spend, so this difference cannot be assigned to individual addresses without defeating that privacy.
Issuance shares use TotalIssuance, so displayed shares across accounts can add up to more than 100%.
What outbound history proves
An ordinary outbound transfer proves an address is transparent; no outbound transfer proves nothing. A dormant ordinary holder can look the same as an encrypted account. A balance with no outbound transfer recorded is an upper bound and may include coins already distributed privately. We do not assign the measured balance gap to individual addresses.
The filter shows the top 100 accounts with a positive free-plus-reserved balance and an ordinary outbound transfer recorded from genesis through this snapshot; ranks remain those of the full list.
The Quantus Treasury label comes from TreasuryPallet.TreasuryAccount storage read at the snapshot block. It is omitted if that read is unavailable.
Labelled service accounts
Some service accounts carry a label so that their balance is not read as one holder. The labels are our inference from public on-chain flows, not a statement by the operator, and not an audit of reserves. The NEAR Intents bridge account holds the QTC behind qtc.omft.near on NEAR: on 8 and 9 October 2026 its balance matched that token’s total supply on NEAR within about 6 QTC. Each user deposits through a personal deposit address that forwards to this account, and a separate fee account tops up those deposit addresses with about 0.001 QTC first.
Website logs
Requests to qtcscan.com are recorded in standard web-server access logs: IP address, time, request, referring page and browser. The logs rotate daily and are kept for 14 days to operate and secure the site. From them we keep daily counts only: visitors, page views, the most visited pages and the domain names of referring websites. The explorer itself sets no cookies and loads no third-party analytics.