Explore QRL 2.0 with ZondScan

Find an address, transaction or block

1. Open zondscan.com. Check the network label so you know which test network you are viewing.
2. Paste a full Q-prefixed address, a transaction hash or a block number into the search field.
3. Submit the search. ZondScan opens the matching address, transaction or block page.
4. If you cannot find a recent transaction, check the network and copied hash, then check again after the explorer has indexed it.

Public addresses and transaction hashes are safe inputs for an explorer. Never enter a seed phrase or private key. QRL 2.0 addresses start with Q; copy the complete address when comparing it with a wallet.

Read an address page

An address page shows its native balance and indexed activity. Amounts are displayed in Quanta. Depending on the address, you can also inspect token balances, token transfers, NFTs or contract information.

1. Copy your receiving address from MyQRLWallet and search for it.
2. Compare the full address shown by ZondScan with your wallet. Check the balance and recent transactions.
3. Open a transaction to inspect the sender, recipient, value and result. For a token transfer, check the token contract as well as its displayed name.

An address balance belongs to the network shown by the explorer. Testnet balances have no monetary value.

Check a transaction

1. Open the transaction hash from your wallet, a dApp or the explorer search.
2. Read the status. A pending transaction is waiting for inclusion. A successful receipt means execution completed. A failed transaction reverted and can still have a network fee.
3. Check the full From and To addresses, transferred value, block and timestamp.
4. Review the transaction fee in Quanta. Pending transaction pages also show the gas price in Shor and the gas limit.
5. For a contract call, inspect the decoded transfers, event logs and internal calls when available. One transaction can contain several token movements.

Block inclusion and finality are separate stages. Use the confirmation information and the network's finalized epoch to judge progress. The transaction guide explains the individual fields.

Browse blocks

1. Open the blocks list, or search for a block number.
2. Select a block to inspect its hash, timestamp, transaction count and gas details.
3. Open a transaction in that block to follow the action it recorded. Use the linked addresses to continue exploring.

The consensus chain organizes time into slots. Some slots have no proposed block. Use the epoch view when you want to see proposed and missed slots together.

Follow validators and epochs

1. Open Validators. Review the active, pending, exited and slashed counts, together with the total stake.
2. Select a validator index. Its detail page shows status, effective balance, public key and lifecycle epochs. Follow the withdrawal-address link when one is available.
3. Open the epoch list. Check which epochs are pending, justified or finalized.
4. Select an epoch to inspect its slot table and follow links to proposed blocks.

For the meaning of those duties, balances and exits, read Validators, epochs and staking and our full staking guide.

Compare staking scenarios

1. Open the staking calculator from ZondScan's tools.
2. Set your validator count, network validator count, uptime and network participation.
3. Compare the estimated reward amounts, effective APR and real yield. Expand the advanced assumptions if you want to adjust tips, supply or the display price.
4. Check the model's protocol parameters. Copy link shares your validator count, network validator count, uptime, participation and priority fees. Supply and display price reload from network data when the link opens, so communicate any custom values separately.

The calculator uses network data where available and exposes its assumptions. Its output is an estimate of validator rewards. Testnet Quanta has no monetary value, including when the calculator shows a fiat conversion.

Inspect and verify contracts

The smart-contract directory links to deployed contracts. Where source is verified, ZondScan can display the source, ABI and compiler settings. Read and write interfaces are available for supported contracts. Writing to a contract requires a wallet approval and may spend Quanta.

Compiler support: the verification page lists the Hyperion compiler builds it offers. Contracts compiled with the IR pipeline (viaIR) cannot be verified yet.

To verify a contract:

1. Enter the deployed Q-prefixed contract address and the exact contract name.
2. Supply the Hyperion .hyp source, any imports and the compiler settings used to deploy it. Match the optimizer settings and provide constructor arguments where applicable.
3. Select Verify & Publish. The service recompiles the source and compares its runtime bytecode with the deployed contract.
4. Check the verification result and published source on the contract page.

Verification establishes a match between source and deployed code. It does not establish that a contract is safe. The deployment and verification guide explains the workflow; confirm current network and compiler settings before using its examples.

Get testnet Quanta from the faucet

1. Copy your wallet's full Q-prefixed testnet address.
2. Open the faucet. Read the current amount, cooldown and any availability notice.
3. Paste your public address, complete the verification challenge and select Request testnet Quanta.
4. Follow the returned transaction link, then check your wallet balance after confirmation.

Faucet amounts and limits can change. Use the values shown on the live page. The faucet needs your receiving address; keep your seed phrase private. See Get testnet Quanta for a longer walkthrough.

Use the learn guides and API docs

ZondScan Learn covers QRL 2.0, post-quantum signatures, units, wallets, transactions, validators, swaps and contracts. Product availability can change after an article is published. Our staking guide includes the current QuantaPool status.

The API docs describe the public REST API for blocks, transactions, addresses, tokens, validators, gas and contract tools. They include request parameters, response formats, rate limits, examples and an OpenAPI specification.

1. Open API Docs and choose the endpoint for the data you need.
2. Read its parameters and limits. Public data endpoints work without an API key.
3. Use the documented example or Try it link to inspect a response. Check each endpoint's amount units before displaying values.

Continue with connecting to a dApp or testnet swaps, then use ZondScan to follow the resulting transactions.