How Does a Solana Token Scanner Work?

The technical pipeline from token launch to analysis display

A Solana token scanner is an automated system that continuously monitors the Solana blockchain for newly launched trading pairs, fetches relevant data about those tokens from multiple sources, applies scoring algorithms to assess their characteristics, and displays the results in a usable interface.

This page explains the conceptual pipeline of how token scanning works, using this platform as an example. The same fundamental approach applies to most automated token scanners, though implementations vary.

The Scanning Pipeline

1. Discovery: Finding new token pairs
Market data

The scanner queries decentralized exchange (DEX) aggregator APIs — in this case, DexScreener — at regular intervals. DexScreener indexes new Solana trading pairs as they are created. The scanner filters these results to find pairs that were created within a specific time window (e.g., the last 60 minutes) and that meet minimum liquidity thresholds.

2. Token Identification: Extracting the token address
Market data

From the new pair data, the scanner extracts the base token's Solana mint address. This is the unique identifier for the token on the blockchain. All subsequent data fetches use this address as the primary key.

3. Market Data: Liquidity, volume, price
Market data

For each discovered token, the scanner fetches current market data including liquidity pool depth, 24-hour trading volume, current price, market cap (if available), and transaction counts broken down by time period (24h, 6h, 1h). This data comes from DEX aggregator APIs and reflects current trading conditions.

4. On-Chain Authority Data: Mint and freeze authority
On-chain data

Using a Solana RPC provider (this platform uses Helius), the scanner fetches the token's on-chain metadata. This includes the current mint authority address (or null if disabled), the freeze authority address (or null if disabled), and basic token program settings. This data comes directly from the Solana blockchain and is not intermediated by any third party.

5. Holder Data: Distribution and concentration
On-chain data

The RPC provider is also queried for the top token holders — the wallet addresses with the largest balances. This data is used to calculate holder concentration (what percentage the top 10 wallets hold collectively) and to estimate holder count.

6. Independent Risk Assessment: RugCheck analysis
Derived data

An independent risk assessment API (RugCheck) is queried for the token address. RugCheck performs its own analysis and returns a risk score and a list of detected risk factors. This provides a cross-reference point that is independent of this platform's own analysis.

7. Hard Filtering: Minimum quality thresholds
Heuristic filter

Before scoring, the scanner applies hard filters. Tokens that do not meet minimum criteria are excluded entirely and not stored or displayed. Current hard filters include: minimum liquidity ($1,000), minimum holder count (2), maximum holder concentration (98%), and maximum volume-to-liquidity ratio (150×). These filters are designed to exclude obvious non-starters.

8. Scoring: Trust Score and Momentum Score
Derived metrics

For tokens that pass the hard filters, the scanner computes multiple scores. The Trust Score aggregates six weighted on-chain factors into a single 0–100 number. The Momentum Score aggregates four activity signals (volume acceleration, buy pressure, holder growth, liquidity depth) into a separate 0–100 number. A Smart Money signal checks whether any tracked wallet addresses appear in the holder data.

9. Storage: Persisting to database
Database

The token data, metrics, and scores are stored in the platform's database. This allows for historical comparison across scans and powers the re-evaluation system that checks whether previously discovered tokens have degraded in quality.

10. Presentation: Display and re-evaluation
Application layer

Stored tokens are served to the web interface via API, with the most recently discovered tokens appearing first. A separate re-evaluation process runs periodically to check whether existing tokens have expired (older than 60 minutes) or have degraded past quality thresholds (collapsed liquidity, zero holders, etc.). Degraded tokens are hidden from the dashboard.

Key Distinctions

On-chain data

Data that comes directly from the Solana blockchain. It is objective and verifiable. Examples: mint authority status, holder balances, token supply.

Market data

Data from DEX aggregators that reflects current trading activity. Examples: liquidity pool depth, volume, price, transaction counts.

Derived metrics

Scores and signals computed from on-chain and market data. Examples: Trust Score, Momentum Score, concentration percentage. These are heuristic interpretations, not absolute measurements.

Limitations of Automated Scanning

  • The scanner captures data at a single point in time — conditions change continuously
  • On-chain data reflects what is observable on the blockchain, not intent or off-chain behavior
  • Sophisticated actors can structure tokens to pass automated filters while still posing risks
  • Third-party API availability affects data completeness — timeouts produce fallback values
  • Derived scores are heuristics based on observed patterns, not provable causal relationships
  • New token contract patterns may not be recognized by existing filter logic

FAQ

How often does the scanner run?

The scanner runs every 5 minutes. Each run queries for tokens launched in the preceding time window, so newly launched tokens typically appear within 5–10 minutes of creation.

Why do some tokens disappear from the dashboard?

Tokens are automatically removed when they exceed 60 minutes of age, when their liquidity collapses below a threshold, when holder count drops to zero, or when other quality re-evaluation criteria are triggered.

Does the scanner catch every new Solana token?

No. The scanner filters for tokens that have at least $1,000 in liquidity and at least 2 holders. Many tokens are created with no liquidity or as test deployments and are excluded. Additionally, the scanner relies on DEX aggregator APIs that may have their own indexing delays.

Can I analyze a token not in the scanner?

Yes. The Contract Analyzer tool accepts any Solana token address and fetches fresh live data from all the same sources — including tokens that predate the scanner or failed the initial filters.