Dexscreener

Reference guides

Dexscreener is a real-time DEX pair chart and on-chain trade monitor

Dexscreener is a live market dashboard for decentralized exchanges - trading venues run by smart contracts - and liquidity pools, where paired tokens trade. Its custom indexer reads blockchain logs in real time, then turns pool activity into price charts, volume, liquidity, trades, and valuation fields. Readers use it to discover pairs across chains, compare venues, follow market activity, and open a trading route without surrendering control of their keys.

The short version: It is a multichain DEX analytics platform that processes on-chain data in real time, helping traders compare pair prices, volume, and liquidity.

Stop searching by ticker alone

A contract or mint address identifies the asset and network behind a search result. Dexscreener search accepts token names, symbols, token addresses, and pair addresses, yet unrelated assets regularly reuse the same symbol.

On Ethereum Virtual Machine networks, an address encodes 20 bytes. It appears as 40 hexadecimal characters, or 42 characters when the 0x prefix is included. A Solana public key encodes 32 bytes, while its Base58 representation spans 32 to 44 characters. These structural facts make a pasted address far more useful than a familiar logo.

Network identity matters just as much. Ethereum mainnet uses chain ID 1, BNB Smart Chain uses 56, Polygon PoS uses 137, Base uses 8453, and Arbitrum One uses 42161. Cross-check an EVM address with Etherscan or an appropriate Blockscout explorer. Solscan provides the equivalent account and mint inspection for Solana.

Two pools containing the same token can show different prices because each pool has separate reserves and trades. Choose the result whose base token, quote token, DEX label, and pool address match the intended market.

Build the first screen from a chain and pool

A first Dexscreener screen should establish the chain, token address, and relevant liquidity pool. Select the network, paste the address, and compare the resulting pair rows before opening a chart.

Automatic listing starts after a token enters a tracked liquidity pool and that pool records at least 1 transaction. A new listing therefore confirms observable pool activity, not complete project metadata or broad trading depth. Check the base and quote assets, venue, pair age, liquidity, and recent transaction count together.

Venue labels clarify where activity occurred. Solana tokens frequently appear in Raydium and Orca pools. Ethereum results include Uniswap V2 and Uniswap V3, while Aerodrome is prominent on Base and PancakeSwap operates on BNB Smart Chain. Select the actual pool rather than whichever row displays the most striking percentage change.

TradingView Advanced Charts provides bars, candles, lines, areas, and Heikin Ashi views. Available timeframes run from 1 minute to 1 month. Short intervals expose individual bursts of activity; longer intervals make the wider price structure easier to read.

What does the pair chart actually measure?

The pair chart measures swaps executed in one specific liquidity pool. Each candle aggregates those trades during the selected interval; it is not a centralized-exchange order book or a composite price assembled from every market.

The quoted price expresses one base token in units of the quote token. A separate USD value relies on the platform's conversion path for that quote asset. Very small values reflect token denomination as well as price: 1 ETH equals 10 ¹⁸ wei, while 1 SOL equals 1 billion lamports. Token decimals determine how raw balances become human-readable amounts.

Pool mechanics also shape the chart. Uniswap V2 deducts a 0.30% swap fee from the input amount, whereas Uniswap V3 stores a fee tier as part of each pool's configuration. Raydium and Orca use their own pool programs and fee settings. Fees, reserve changes, and arbitrage move each venue's displayed price along its own path.

Buy and sell labels describe movement relative to the selected base token. Reversing the pair orientation reverses that interpretation. Read the pair name before treating a transaction count as evidence of directional pressure.

Liquidity, volume, trades, and valuation belong together

Pair metrics answer different questions about one market. Liquidity describes the assets presently available in the pool, volume totals executed swap value over a chosen window, and transaction counts record events rather than their size.

High volume against shallow liquidity indicates rapid turnover and greater price-impact exposure. Numerous transactions from a small maker set describe a different market from the same count spread across many addresses. Buy and sell totals also need their corresponding volume: 100 small swaps need not outweigh one much larger trade.

Fully diluted valuation follows the formula (total supply − burned supply) × price. Market capitalization uses circulating supply when an applicable figure is available, including supply information submitted through Enhanced Token Info or supplied through CoinGecko. Neither field measures cash held by the pool. Compare valuation with actual liquidity before drawing conclusions about market depth.

Prices can diverge between pools until arbitrage closes the gap. Thin reserves, distinct quote assets, and uneven activity explain much of that difference. Comparing several pools for the same address reveals whether one chart represents the main market or an isolated venue.

Move from observation to a signed swap

The trading handoff moves from analytics into an external or integrated swap flow. A Dexscreener pair page supplies market context, while the selected DEX front end or router constructs the quote and transaction that a wallet signs.

MetaMask keeps EVM account keys under the user's control, and Phantom performs that role on Solana. Before signing, inspect the active chain, input asset, output asset, expected output, route, price impact, and network fee. Pool fees and price impact are separate from the blockchain fee.

Solana charges a base fee of 5,000 lamports per signature, plus an optional prioritization fee. A Solana transaction has a maximum serialized size of 1,232 bytes and a maximum compute limit of 1.4 million compute units. Ethereum gas cost instead reflects gas consumed, the block's base fee, and the chosen priority fee.

An ERC-20 swap might require a preceding allowance transaction when the router lacks sufficient authorization. SPL Token transfers do not use the ERC-20 allowance mechanism. After confirmation, Etherscan or Solscan shows the authoritative transaction state before the analytics indexer incorporates the resulting trade.

Choose a screener, explorer, or DEX front end by task

Crypto analytics tools differ by the question they answer. A screener discovers and compares pools, an explorer exposes chain records, and a DEX front end prepares a quote for wallet approval.

GeckoTerminal and DEXTools are direct alternatives for pool discovery. Solscan serves a narrower verification role rather than replacing a multichain screener. Jupiter focuses on finding Solana swap routes, while Uniswap supplies a DEX front end for its own protocol. Many research sessions use both a screener and an explorer because their records answer different questions.

Treat trending rank and profile polish as context

Trending rank combines market activity, community engagement, and profile signals into a discovery score. Its stated inputs include liquidity, volume, transactions, unique makers, holders, page visits, reactions, verification, and third-party audit information. The precise weighting remains undisclosed.

Boosts apply a multiplier to a token's Trending Score rather than replacing those inputs. Boost packs last from 12 to 24 hours, and their active count is visible. A Golden Ticker appears at 500 active Boosts and remains while that threshold holds. A token inactive for more than 24 hours is ineligible for boosting.

Rank, Boost count, and polished metadata do not establish pool depth or broad ownership distribution. Enhanced Token Info adds presentation fields such as descriptions and social links, while reactions capture community attention. Keep those signals separate from reserves, maker activity, transaction history, and the token contract's actual configuration.

Scale the workflow with alerts and the API

Monitoring automation turns a manually selected pair into a repeatable data feed. Alerts track chosen conditions, while the public API exposes pair search, token pools, profiles, Boost data, advertisements, and paid-order status.

Pair responses contain the chain, DEX, pair address, base and quote tokens, native and USD prices, transactions, volume, price change, liquidity, valuation, creation time, profile information, and active Boosts when available. Store chain and pair identifiers together because an address without its network context is ambiguous.

The public API caps pair, search, and token-pair routes at 300 requests per minute, profile, Boost, advertisement, and order routes at 60 requests per minute, and the multi-token route at 30 comma-separated addresses per call. Caching stable identifiers and deduplicating repeated requests keeps monitoring within those limits.

Alerts and filters are most useful after the correct pool has been established. Start with address identity, interpret chart and liquidity data as one pool's record, and keep transaction signing separate from observation. That sequence produces a cleaner view of fast-moving decentralized markets.

Practical questions about Dexscreener

First published 4 Aug 2026