How to use DexScreener? (Real-time tracking)

Understanding DexScreener Interface

1. DexScreener provides a clean dashboard showing trending tokens across major decentralized exchanges including Uniswap, PancakeSwap, and Raydium.

2. The homepage displays real-time price charts, liquidity depth, trading volume, and pair addresses without requiring wallet connection.

3. Each token card includes a color-coded volatility indicator and a 24-hour change percentage rendered in bold green font for immediate visual recognition.

4. Users can filter by chain—Ethereum, BSC, Solana, Arbitrum, Base—and apply custom timeframes from 5 minutes to 1 week directly on the chart.

5. Clicking any token opens a dedicated page with candlestick charts, order book visualization, and swap simulation tools powered by on-chain data feeds.

Navigating Token Pair Analysis

1. Every token pair shows bid-ask spread calculated live from DEX router contracts, updated every 3–7 seconds depending on chain congestion.

2. Liquidity pool composition is broken down into reserve ratios, showing exact token amounts and USD-equivalent values per asset.

3. Historical swap count graphs highlight peak activity windows, often correlating with whale movements detected via cluster analysis of transaction signatures.

4. The “Top Traders” tab lists wallet addresses ranked by cumulative volume over the past 24 hours, with each address linked to Etherscan or Solscan.

5. A red warning icon appears when slippage exceeds 8% on low-liquidity pairs, prompting manual review before initiating trades.

Setting Up Real-Time Alerts

1. Alert configuration requires selecting a token pair, then choosing triggers such as price crossing a threshold, volume spike above 200% of 24h average, or new liquidity addition exceeding $50k.

2. Notifications deliver via Telegram webhook integration using bot tokens generated inside DexScreener’s settings panel.

3. Each alert includes raw blockchain data: block number, timestamp, transaction hash, and decoded function call parameters.

4. Users may configure multiple alert profiles—one for pump detection, another for rug pull indicators like sudden LP removal or owner address changes.

5. Alert history remains accessible for 72 hours and exports as CSV containing all triggering events with millisecond precision timestamps.

Interpreting On-Chain Signals

1. The “Contract Audit” badge pulls verified status from CertiK and OpenZeppelin, displaying audit date, scope limitations, and critical severity findings if present.

2. Token distribution heatmaps reveal concentration levels; wallets holding more than 5% of supply are flagged with orange borders and labeled “Whale Holder”.

3. Transfer velocity metrics track how fast tokens move between addresses—abnormal acceleration often precedes coordinated dumps or exchange listings.

4. Burn rate graphs show ETH or BNB spent on token burns, with burn transactions cross-referenced against contract event logs for authenticity verification.

5. Router compatibility checks confirm whether a token supports seamless swaps across aggregators like 1inch or Matcha, based on bytecode signature matching.

Frequently Asked Questions

Q: Does DexScreener support private RPC endpoints?A: Yes—users can input custom RPC URLs under Settings > Network Configuration to route queries through self-hosted nodes or enterprise providers like QuickNode.

Q: Can I track tokens deployed on Layer 2 chains like zkSync or Starknet?A: Currently supported chains include Ethereum, BSC, Polygon, Arbitrum, Optimism, Base, Solana, and Avalanche. zkSync and Starknet are not yet integrated but appear in roadmap documentation.

Q: How does DexScreener calculate market cap for tokens without CEX listings?A: Market cap is derived exclusively from on-chain liquidity pool reserves multiplied by the latest weighted average price across all active DEX pairs on supported networks.

Q: Are historical candlestick data points sourced from on-chain events or third-party APIs?A: All OHLCV data originates from raw swap events emitted by DEX routers, parsed and aggregated by DexScreener’s indexer running on AWS EC2 instances synced with full archival nodes.