Solana token screening begins with the mint address and token program. The scanner then decodes mint and freeze authorities, token extensions, supply, token-account concentration, liquidity pools, quote assets, price impact, launch activity, metadata, and project evidence. Automated trading and short histories make context essential.
Keep each data family traceable so one attractive metric cannot silently override missing identity, liquidity, supply, or control information.
Store mint address, token program, decimals, supply, metadata, creation timeline, and provider mappings.
Surface mint, freeze, metadata, delegate, and other relevant authorities with control and revocation status.
Decode transfer fees, hooks, delegates, non-transferability, metadata features, and other enabled behavior.
Show raw and adjusted concentration, known pools and program vaults, active accounts, and balance retention.
Map major pools, quote assets, fee design, active liquidity, volume, trade count, routes, and price impact.
Separate unique participation from bots, repeated small trades, arbitrage, launch automation, and failed transactions.
A useful scan is a documented sequence with clear failure states, not a mysterious score that always produces a candidate.
Confirm the mint across first-party sources, pools, explorers, and data providers before joining any record.
Read token program, authorities, extensions, supply, token accounts, metadata, and related program behavior.
Inspect pools, routing, liquidity, volume, trade distribution, price impact, and SOL-relative chart context.
Reject uncertain records, monitor short histories, or investigate product use and token utility with a saved snapshot.
Scanner results become more trustworthy when their blind spots are displayed beside the output.
Transaction count and early volume can be dominated by routers, bots, arbitrage, and launch competition.
Names, symbols, images, and URIs may change or disappear and should not replace the mint address.
One owner can control multiple token accounts, while custodians and program vaults can represent many users.
Move from the page-level framework into a detailed, source-linked research workflow.
Build a Solana token scan around mint identity, supply and freeze authorities, token extensions, liquidity, holders, transaction activity, token age, and execution quality.
Read the guide →
A structured checklist for verifying a new token’s identity, contract controls, supply, holders, liquidity, deployer history, market data, and project claims.
Read the guide →
A step-by-step method for turning a broad token universe into a focused research list using liquidity, market structure, supply, onchain, and risk filters.
Read the guide →The mint address on a specific token program. Names and symbols are metadata and can be duplicated.
It is an authority that can create additional units when the mint permits it. The scanner should show whether it exists and who controls it.
Extensions can change transfer fees, control, metadata, delegates, hooks, or other behavior that affects holders and markets.
Not necessarily. Bots, routers, airdrops, and repeated automated actions can produce large counts.
Start with a defined universe, combine independent signals, and record why each candidate survives or fails the scan.