- What's the difference between this and the transactions feed?
- The transactions feed (/transactions) shows every signed transaction — one row per signature. This feed (/token-transfers) shows decoded QRC-20 Transfer events emitted BY those transactions. One transaction can emit many transfer events (e.g. a Uniswap swap moves two tokens in one tx → two rows here). NFT transfers (QRC-721/1155) have their own /nft-transfers feed, and new NFTs appear on /nft-mints.
- What's the difference between Mint, Burn, and Transfer?
- Mint and Burn are the same underlying event as Transfer, but with a special party: Mint is a Transfer where the FROM address is the zero address (Q000...000) — meaning the tokens are coming into existence. Burn is a Transfer where the TO address is the zero address — meaning the tokens are being destroyed (sent to an unrecoverable address). Everything else is a regular Transfer between two wallets or a contract.
- Why don't I see NFT transfers here?
- We keep this hub strictly fungible (QRC-20) to match the conventional block-explorer split — Etherscan does the same with /tokentxns vs /tokentxns-nft. NFT collection transfers (QRC-721) and multi-token transfers (QRC-1155) live on their own /nft-transfers feed (with the collection leaderboard at /top-nft). The backend serves both from the same endpoint via ?token_standard=qrc721 for power-users.
- Why don't token transfers from the original QRL chain show up?
- The original Proof-of-Work QRL chain uses a native token_create + transfer_token transaction subtype (not contract events). Indexing those into a per-event feed requires additional ETL Silver-layer work that hasn't been prioritised, since active token analytics focus on QRL 2.0. The transactions themselves are still visible via /qrl-legacy/transactions.
- How do I know a QRC-20 token is genuine?
- Verify it by its contract address, not its name or symbol. Anyone can deploy a QRC-20 token with a copied name or ticker, but the contract address is unique. Click the token to open its page and confirm the address matches the one you expect from the project — the symbol alone is not proof.
- What does the Amount column show, and what if it says a huge number like 1,000,000,000,000,000,000?
- Amount is the transferred value, decimals-corrected when the token's decimals() metadata is known (e.g. 18 decimals on a QRC-20 contract means 1,000000000000000000 raw units = 1 token). When metadata fetching failed for the contract, we fall back to the raw uint256 amount with a tooltip flag — a 19-digit number usually means '1 token of an 18-decimals contract', not a billion tokens.
- Why is a transaction I expected to see here missing?
- This feed only lists transactions that emit a valid QRC-20 Transfer event in their receipt logs. Three reasons your expected tx might not appear: (1) the contract uses a non-standard event signature instead of the canonical `Transfer(address,address,uint256)` — it'll still appear on /transactions as a generic contract call; (2) the transaction reverted (status = 0), so no events were emitted at all — it shows on /transactions with the failed status icon; (3) the token is a QRC-721 NFT or QRC-1155 multi-token, which are decoded but kept on the /nft-transfers feed rather than mixed with fungibles here.