Methodology & Data Sources
Data sources
All chain data is read from nodes that Quantascan operates. No third-party indexing API sits in the pipeline.
- QRL (Proof-of-Work, XMSS): a QRL node, read over its gRPC API.
- QRL 2.0 (Proof-of-Stake, ML-DSA-87): an execution client (gqrl) over JSON-RPC and a consensus client (qrysm) over its beacon API.
- Price: the QRL/USD price comes from CoinGecko and is used only for USD values. No figure on chain activity depends on it.
- Labels: exchange, pool and foundation labels are curated and reviewed before they go live. Exchange deposit addresses are detected from on-chain behaviour and re-checked daily.
Processing
Each block passes through three stages:
- Raw: the node's response is stored unchanged, so any later stage can be rebuilt without fetching the chain again.
- Normalised: blocks, transactions, withdrawals, logs and internal transfers are decoded into one schema per chain. QRL 2.0 transaction status and fees come from the transaction receipt.
- Aggregated: daily series, balances, rankings and supply figures are computed from the normalised data. Charts and headline numbers read from this stage.
When the chain replaces a block (a reorganisation), the replaced block's data is removed and the affected aggregates are rebuilt.
Checks
- Indexed blocks are compared with the node by height and block hash. Missing or mismatched blocks are re-fetched automatically.
- Every hour, aggregated figures are recomputed from the normalised data and compared. A difference is queued for a rebuild.
- On QRL, every block is checked for exactly one coinbase that pays no more than the block reward plus fees, and the coins the node reports as emitted are tracked for unexpected jumps.
Corrections that change a published figure are listed in the changelog. Service availability is on the status page.
Definitions
| Metric | Definition | Details |
|---|---|---|
| Transactions | Signed transactions. On QRL, block rewards (one coinbase per block) are reported separately and are not counted as transactions. | Transactions |
| Balance | Received minus sent minus fees paid, including internal (contract) transfers on QRL 2.0. Failed QRL 2.0 transactions move no value. | Internal transfers |
| Supply | QRL genesis allocation plus block rewards actually minted on chain. Coins minted on the QRL 2.0 testnet are not included. | Tokenomics and supply |
| Exchange flows | Movements across the boundary of labelled exchange wallets and their deposit addresses. Transfers within one exchange are excluded. | How exchange flows are measured |
| Rich list and distribution | Addresses ranked by balance. One address is not one person: exchanges and pools hold coins for many users. | Understanding the rich list |
| Wallet types and badges | Classified from on-chain behaviour. A curated label always takes precedence over the automatic classification. | Wallet badges |
| Units | Amounts are shown in Quanta. 1 Quanta = 1e9 Shor = 1e18 Planck. | Shor, Quanta and Planck |
| Contract verification | A verified contract's published source compiles to the deployed bytecode. Verification does not audit what the code does. | What source verified means |
Freshness
New blocks are indexed within seconds of confirmation. Aggregated figures are cached for up to a few minutes. Analytics pages state the block and date their figures refer to (“Data as of block #…”).
Licence and API
On-chain data shown on Quantascan is public blockchain data, released under CC0. The same data is available through the REST API (free plan, key required, with its own attribution condition).