Dexscreener pairs are liquidity pools indexed by chain and pair address

Choosing the exact SOL/USDC venue on Solana

A SOL/USDC market selection on Solana starts with the venue and pool account. Raydium and Orca can each host several pools involving those assets, with separate liquidity, fees, trades, and price paths.

Every pool binds exactly two token mint addresses. Wrapped SOL uses 9 decimal places, while native USDC on Solana uses 6. Those precision settings convert integer token amounts into the quantities shown on a chart. They do not identify the market by themselves. The pool account supplies that missing coordinate.

Dexscreener pairs preserve the venue boundary. A Raydium CPMM pool does not merge its reserves with a Raydium CLMM pool, and neither absorbs liquidity from an Orca Whirlpool. Compare the DEX name, pair address, base-token mint, quote-token mint, and reported liquidity together. Matching only SOL and USDC leaves several valid markets in view.

This separation explains small price differences between charts. Each pool receives its own swaps and liquidity changes. Arbitrage links their prices economically, yet every chart still records the events routed through one address.

When identical tickers resolve to different assets

Ticker collisions occur when unrelated token contracts or mints publish the same symbol. Pair identification therefore rests on token addresses and the chain namespace, while names and tickers remain display metadata.

On Ethereum, Base, and Arbitrum, an EVM address contains 20 bytes and is normally rendered as 40 hexadecimal characters after the prefix. A Solana account address contains 32 bytes and is displayed with base58 encoding. The formats are visibly different, but neither format describes the token's economics or its relationship to another pool.

Token precision also comes from the asset contract or mint. The ERC-20 decimals method returns an 8-bit unsigned integer and is optional under the standard; its representable range runs from 0 through 255. SPL Token and Token-2022 mints likewise store a decimals value. Dexscreener uses those on-chain identities when presenting base and quote amounts.

A pair can show familiar symbols while pointing to an unexpected address combination. Read the chain, both token addresses, and the pair address as one record. The same hexadecimal address string can also exist on two EVM networks, where each chain maintains unrelated state.

What does the pair address identify?

A pair address identifies one liquidity-pool contract or program-owned account. Its internal meaning follows the DEX architecture, so the address should be interpreted alongside the chain and protocol.

EVM pool contracts use 20-byte addresses, while Solana pool accounts use 32-byte addresses. On Uniswap v2, the pair contract holds two reserves and also issues ERC-20 liquidity tokens. Its constant-product pools charge a fixed 0.30% swap fee.

Uniswap v3 adds a fee tier to the pool key. Widely deployed tiers are 0.01%, 0.05%, 0.30%, and 1%, paired with tick spacings of 1, 10, 60, and 200. TickMath spans indexes from -887272 through 887272. Two pools containing the same ERC-20 contracts remain distinct when their fee tiers differ. Liquidity positions are represented separately through the NonfungiblePositionManager rather than by the pool address itself. The related steps are listed in Getting started with dexscreener.

Orca Whirlpools derive pool identity from a configuration, two token mints, and tick spacing. One tick represents a 1-basis-point price step, and the supported tick range extends from -443636 through 443636. Raydium's CPMM and CLMM programs use different account layouts and pricing mechanisms. In every case, the address anchors Dexscreener data to one pool implementation.

How one pool's reserves become a market chart

A pair chart represents swaps and liquidity belonging to one indexed pool. Dexscreener processes blockchain events, orders them over time, and derives candles, transaction counts, volume, price changes, and liquidity fields from that stream.

The base-token price expresses one base unit in quote-token units. A USD value requires an available conversion for the quote side; otherwise that field can remain empty. Reserve-style pools expose two balances directly. Concentrated-liquidity pools also require the active price range and initialized ticks to describe executable depth.

Worked example: a hypothetical constant-product swap

All changing inputs in this example are hypothetical. Assume a hypothetical Uniswap v2 pool holds 100,000 USDC and 500 SOL, giving a hypothetical starting price of 200 USDC per SOL. A hypothetical trader supplies 1,000 USDC. The protocol's fixed 0.30% fee removes 3 USDC from the amount used by the pricing curve, leaving 997 USDC.

Using the constant-product swap formula, the output equals 997 × 500 ÷ (100,000 + 997), or 4.93579 SOL. The concrete execution price is therefore about 202.602 USDC per SOL. After settlement, the pool holds 101,000 USDC and approximately 495.06421 SOL. Dexscreener indexes that swap against this pair address. It does not distribute the trade across other SOL/USDC pools.

The example shows why pool depth matters. Two charts can share their token symbols while producing different execution outcomes. Their reserve sizes, active liquidity, fee configuration, and recent order flow belong to separate addresses.

Stable keys for pair-address integrations

A pair-address integration should store the chain identifier and pair address as a composite key. The pair lookup requires both values and returns structured fields such as the DEX identifier, token objects, native and USD prices, transactions, volume, liquidity, valuation data, creation time, and active boosts.

The pair lookup, pair search, token-pairs, and token-address endpoints each allow 300 requests per minute. The multi-token endpoint accepts up to 30 comma-separated token addresses in one request. Profile, order, advertisement, and boost endpoints use a separate limit of 60 requests per minute. These limits belong to endpoint groups, so clients should not treat them as one shared number.

Several response properties are nullable. A newly indexed market might lack a USD price, liquidity valuation, market capitalization, or descriptive information while still returning a valid pair address. Preserve null as missing data rather than converting it to zero. Zero asserts a measured amount; null states that the field was not supplied.

Symbols make readable labels, but addresses make durable keys. Cache records under chain and pair address, retain the returned schema version, and refresh changing metrics without rewriting the market's identity. Token-address discovery serves a different job: it finds the pools containing an asset before the application selects one pair.

How a new pool becomes an indexed record

A new pair record begins with an on-chain pool and trading activity. Dexscreener automatically lists a token after it enters a liquidity pool and the pool records at least 1 transaction.

The indexer parses raw blockchain logs and program activity, then converts those inputs into searchable pair data. Opening the resulting chart is read-only: it submits 0 on-chain transactions and requires 0 wallet signatures. Executing a swap is a separate action handled by the selected DEX and network.

Earlier constant-product designs, including Uniswap v2 and Raydium AMM v4, made one pool address the natural market boundary. Concentrated-liquidity systems such as Uniswap v3, Orca Whirlpools, and Raydium CLMM added configuration choices that permit several pools for the same assets. Fee tiers and tick spacing made precise pair resolution even more important.

In most cases, Dexscreener pairs consequently form an address-level market index. A complete reading follows the chain, DEX, pair address, two token addresses, and observed pool data in that order. That sequence keeps a familiar ticker from being mistaken for a unique market.