- What is an NFT transfer event, and how does it work on QRL 2.0?
- When an NFT moves between addresses (or is minted or burned), the contract emits a Transfer event in the transaction's receipt logs. Quantascan's ETL watches every block, decodes those events using the standard QRC-721 / QRC-1155 event signatures, and writes one row per emitted event into our index. This page is the live feed of those decoded events — one row per movement, not per parent transaction.
- What's the difference between this feed and /token-transfers?
- Same Transfer-event shape, different filter. /token-transfers shows QRC-20 fungible transfers (where 'amount = 5 USDC' means 5 units). /nft-transfers shows QRC-721 + QRC-1155 transfers — each row moves a specific `tokenId`. The Method column detects Mint (from = Q000…000), Burn (to = Q000…000), and regular Transfer the same way on both pages.
- What's the difference between Mint, Burn, and regular Transfer?
- All three are the same Transfer event under the hood — they differ only by who's on each side. Mint: the FROM address is the all-zero address (Q00…00), meaning a brand-new tokenId is coming into existence. Burn: the TO address is zero, meaning the tokenId is being destroyed. Regular Transfer: both sides are real addresses, meaning ownership is changing hands. Quantascan classifies the row using exactly this zero-address heuristic, which matches how Ethereum tooling treats it.
- Why is the Amount column always '1' for QRC-721?
- QRC-721 is one-of-one by design — each tokenId has exactly one owner at a time, so 'amount' isn't a meaningful concept and the standard always reports it as 1. QRC-1155 is multi-token: a tokenId can have many copies (e.g. 100 of a common game item, 1 of a rare drop), so Amount varies per transfer. The standard pill on each row tells you which case applies.
- What does the Token ID column show?
- For QRC-721, the unique tokenId of the moved NFT (e.g. CryptoPunk #1234). For QRC-1155, the tokenId category — multiple copies of the same tokenId can exist, so the Amount column tells you how many were moved in this transfer. Click the Token ID to open that specific NFT's provenance page (full transfer history for that single token).
- What's a QRC-1155 batch transfer, and why do I see multiple rows for one transaction?
- QRC-1155 has a special TransferBatch event that moves multiple tokenIds in a single transaction (efficient for game inventories, multi-mint drops). Quantascan expands each (tokenId, amount) pair from the batch into its own row, so one batch event with 100 tokenIds shows as 100 rows on this page — but they all share the same `log_index` and a `batch_size=N` flag, so you can spot they came from one batch. The Method column still says Mint / Transfer / Burn per row.
- Why might my NFT transfer be missing from this feed?
- Three reasons. (1) The contract emits a non-standard event signature instead of the canonical `Transfer(address,address,uint256)` or `TransferSingle/TransferBatch` — it'll still appear on /transactions as a generic contract call, just not here. (2) The transaction reverted (status = 0), so no events were emitted at all — visible on /transactions with the failed status icon. (3) The token is QRC-20, not QRC-721 / QRC-1155 — those transfers live on /token-transfers.
- How do I see all transfers of one specific NFT?
- Click the Token ID on any row to open that NFT's provenance page — it shows the complete chain of ownership for that single tokenId, from mint through every transfer up to the current holder, with timestamps and tx-hash links. The URL is `/nft/{contract}/{tokenId}` if you want to deep-link.