- What did this contract call actually do?
- The Action headline shows the function selector (or its decoded human name when Quantascan has the ABI). The contract address called is the To field; whatever it changed under the hood is reflected below — the Transfer diagram (native value, the fee, and any token movements it emitted) and the Decoded token transfers card (if the contract emitted QRC-20/721/1155 Transfer events). The More Details collapsible shows the raw calldata for full byte-level audit.
- Why is the Amount usually zero on a contract call?
- Most contract calls don't move native QRL2 at the top level — they move token balances inside the contract's own storage, which doesn't count as a native transfer. The token movement is what the Decoded token transfers card surfaces (when present). When you see Amount > 0 on a contract call, it means the sender attached native QRL2 alongside the call (typical for swap-in flows or contract deposits).
- How can I tell if this transaction is final?
- Look at the Finality badge in the action header. It starts as 'head' (just landed, still being attested by the validator committee), advances to 'justified' after one epoch (~2h 8min) and reaches 'finalized' after two epochs (~4h 16min) — at which point the protocol guarantees the transaction can never be reversed (an attacker would need to control more than one-third of total stake and willingly slash it). Most wallets treat 'head' as safe for everyday transfers; exchanges and high-value transfers conventionally wait for finalization.
- How was the fee on this transaction calculated?
- On QRL 2.0 the fee is gas_used × effective_gas_price, sourced from the transaction's receipt — not the upper-bound max-fee the sender originally signed. The effective gas price is the confirming block's EIP-1559 base fee plus the sender's optional priority tip (capped at the signed maximum). The base fee is destroyed by the protocol; only the priority tip reaches the proposer.
- Will the contents of this transaction ever change?
- No. Once a transaction is included in a finalized block its hash, sender, recipients, value moved, fee paid, status, and emitted event logs are part of the historical record forever. The URL of this page is also stable: bookmarking or sharing it always returns the same data, even years from now.
- Where does this data come from?
- Quantascan indexes from a QRL 2.0 archive node we operate ourselves — no third-party API in the pipeline. The transaction body comes from the chain client (qrl_getTransactionByHash — QRL 2.0 uses the qrl_* JSON-RPC namespace, not eth_*), the receipt (status, gas used, effective gas price, contract address, logs) is fetched in parallel, and reorgs are auto-detected so what you see always matches the canonical chain.