Contract basics
Name, symbol, decimals and total supply are called on the token itself, together with the size of its deployed code. No code at the address is the first warning.
Features
A token's own website shows what its team wants you to see. The chain shows what the contract can actually do. These are the parts Lummiq reads.
Name, symbol, decimals and total supply are called on the token itself, together with the size of its deployed code. No code at the address is the first warning.
Selectors for mint, pause, blocklist, fee changes, trading switches, upgrades and forced burns are pulled from the bytecode and from the logic contract behind a proxy.
owner() and getOwner() are both tried. The result says whether the owner is a plain wallet, a contract, the zero address, or whether the token has no owner function at all.
The standard proxy slots are read straight from storage. If someone can point the token at new code, the logic contract, beacon and admin are listed with explorer links.
Source verification is checked on Sourcify, then on the explorer. Unverified code is flagged as something to look at, not as proof of bad intent.
Official stock tokens on the chain carry the issuer's beacon in their code. A token that only borrows the ticker does not, and the scan says so.
The ten largest balances as a share of total supply, each marked as wallet or contract. When the explorer is out of reach, the scan falls back to balances of recently active addresses and labels the result as a floor.
Give it any address and read its ETH balance, transaction count, tokens it moved recently, the counterparties it deals with most and the token approvals it still has open.
Unlimited allowances that a wallet granted and never revoked are listed per spender, so you can decide which ones to close in your own wallet.
Recent Transfer events are read in windows from the head block: how many, how many distinct senders, whether one address drives most of them and whether the last hour spiked.
Pool depth, number of pairs, 24 hour volume and price come from public DEX data for the chain. Re-run the scan to see how the numbers moved; nothing here is a price promise.
Every scan produces a canonical report and its keccak-256 fingerprint. Download the report as JSON and anyone can recompute the same fingerprint.
Anchor a fingerprint with one transaction from your wallet. The log records the token, the block of the reads and the rules version, and keeps the first anchor of every report.
Paste a report you were sent. The page recomputes its fingerprint in your browser and looks it up on chain, so an edited report can never match.
Some networks intercept the chain's public endpoint. Reads go through the site's own read-only relay first, then fall back to public endpoints.
Star tokens on the scanner board. The list lives in your browser only and never reaches a server.
The token is not needed for anything on this site today. These are the uses the team is considering; none of them is live, and none of them promises a return.
Deeper history and saved monitoring for $LUMMIQ holders. A plan, not a feature of this build.
Metered access to the scan API for bots and dashboards, paid in credits. Not available yet.
Notices when an owner changes, a proxy is upgraded or concentration jumps. Not available yet.