DEX screener
Screener turns indexed DEX trades into token pair market data
· updated
Screener converts recorded trades on decentralized exchanges (DEXs) into charts and metrics for individual token pairs through blockchain indexing. The displayed history depends on supported markets, correctly interpreted token amounts, and processed transactions. Understanding that conversion explains why a completed swap, a chart update, and a volume change can appear at different times.
Bottom line: A pair chart reflects indexed market activity, so its address, units, and time window determine what its numbers mean.
Pool records connect individual swaps to market history
A pool supplies the market context that lets an indexer connect an individual swap with the correct token pair and its accumulated history. The blockchain records execution; the indexer organizes those records into data that a chart can use. A chart then groups prices across time, while volume measures activity within a defined period.
That relationship makes the pool address part of the meaning of every displayed number. Separate pools containing the same token have separate trading histories. Combining their activity produces a different dataset from displaying a single pool. Before interpreting an apparent disagreement, establish whether both displays describe the same market. Filters operate on these resulting metrics, so their matches also depend on the underlying data and selected period.
Token units determine the meaning of a price
Trade amounts need a consistent unit and direction before they can describe a price that a reader can interpret or compare.
Amounts must use the token's decimal precision
Raw token amounts can use integer units that differ from the quantities shown to people. Decimal precision supplies the conversion between those representations. Dividing unadjusted amounts from tokens with different precision produces the wrong human-readable ratio. The conversion belongs before price calculations and volume comparisons.
Displayed rounding adds another distinction. A short price label can hide digits that remain significant when comparing trades. Arithmetic based on rounded screen values can therefore differ from arithmetic using the underlying amounts.
The quote direction defines the ratio
The base token is the asset being priced, and the quote token supplies the price unit. For a simple swap, dividing the quote amount by the base amount gives the average exchange ratio for those recorded amounts. Reversing the direction gives the reciprocal ratio. Neither ratio alone describes every price encountered during execution.
A USD display adds a valuation step. Its meaning includes the conversion used to express the token amount in dollars. Keep the unit attached to the number when comparing records; an amount of quote tokens and a dollar value aren't interchangeable.
Parsed blockchain records become searchable market data
DEX screener's indexer reads blockchain activity and turns it into stored records that support market displays. Its custom indexer parses, analyzes, and stores raw blockchain logs.
Decoding connects recorded values with their meaning in the relevant exchange implementation. A token amount, pool identifier, and transaction reference serve different purposes. Treating every token movement as a trade would mix swaps with other activity. Supporting a blockchain therefore requires more than recognizing its addresses; interpreting a particular exchange also requires understanding the records that its contracts or programs produce.
This creates a boundary around the display. A chart describes the activity that the service has identified and processed for that market. An empty result doesn't establish that the blockchain contains no relevant transaction.
Time windows shape candles and volume
The same trading history produces different chart detail when its observations are grouped into different intervals. Volume also changes with the boundaries of the period being measured.
Candles summarize prices within an interval
A standard price candle summarizes the open, high, low, and close for its interval. Its body describes the relationship between the opening and closing prices, while its wicks show the extremes.
A longer interval can combine more price observations into one candle. It loses detail about the path between those observations. During an unfinished interval, new observations can change the close and extend either extreme. That movement is normal for a developing candle; it doesn't by itself indicate that earlier trades changed.
Volume needs matching boundaries and units
Volume totals trading activity across a specified period. A rolling window moves with the observation time, while a completed chart interval has fixed boundaries. Comparing their totals without aligning those boundaries can create an apparent discrepancy even when both calculations use valid records.
Rolling volume can fall when older trades leave the window. New trading doesn't have to stop for that to happen. Likewise, a change in the chart interval doesn't establish that every nearby summary metric uses the new interval. Read each field's period separately before treating two values as comparable.
A transaction can contain several pool swaps
A blockchain transaction can contain multiple swap events, so its transaction identifier needn't correspond to just one market record. A route through several pools can leave a swap record in each participating pool. Event-level identification distinguishes those records within the transaction. This means that adding pool-level volumes across a route can count successive exchanges within the same overall operation. Pool activity and the amount that a user initially supplied answer different questions.
Indexing determines when recorded activity appears
A completed blockchain operation and an updated market display are separate states because the display depends on processing the relevant records after execution.
Data freshness therefore has several dependencies: blockchain availability, recognition of the exchange's activity, indexing progress, and delivery to the displayed view. A page refresh requests another view of the service's data. It doesn't make the indexer understand an unsupported pool format or guarantee that newer records have reached its stored dataset.
An unchanged price has more than one possible explanation. Recent swaps may have occurred at the same displayed price, or the pool may have had no new swaps. Processing or delivery may also lag. Price alone cannot distinguish those states; transaction references and recorded times provide more useful evidence.
A missing pair calls for a compatibility check
When a requested pair returns no usable history, compare a market-data lookup with direct transaction inspection using the same chain, pool, and transaction reference. Their requirements and returned evidence differ.
- If the service covers the chain and exchange implementation, request the exact pair and check that the returned market identifiers match.
- If the pair resolves but the expected swap is absent, inspect that transaction's execution record before attributing the absence to indexing.
- If coverage is missing, use a compatible blockchain explorer or node interface to inspect execution rather than repeatedly requesting the unsupported market.
- If the transaction completed, match the pool and swap details; a successful transaction status alone doesn't identify every operation within it.
- If the pair's displayed trade history later contains the matching swap, that record has reached the display. A rising price isn't evidence of completion.
Direct inspection can establish that the swap executed even when a chart remains unavailable. It doesn't establish that the screening service will add support or reconstruct the missing history. The fallback answers whether execution occurred while leaving chart availability unresolved.
Derived fields require more than a trade record
A usable swap record doesn't automatically supply every field on a pair page. Price, liquidity, and supply-based valuations require different inputs.
The API represents pair identity separately from market metrics and permits missing values for several derived fields. That distinction matters when moving data into another application. An unavailable value shouldn't silently become a measured zero. Retaining its missing state prevents calculations and filters from treating absent information as a market observation.
Liquidity describes assets available in the pool, whereas volume accumulates exchanges over time. A liquidity addition can change pool holdings without representing swap volume. Valuation introduces supply information alongside price. These relationships explain why fields on the same screen can change for different reasons, even when they describe the same token.
Repeated comparisons need a stable measurement basis
Ongoing monitoring works only when successive observations retain enough context to remain comparable. Keep the chain, pair address, price unit, and measurement period with each saved value.
Record when the observation was retrieved separately from any transaction time that it contains. Retrieval time describes the snapshot you received; transaction time describes activity within that snapshot. Changing pools or periods between observations changes the comparison, even if the token's name remains identical.
Use the pair's indexed history to examine market activity. Use the underlying execution record when the unresolved question is whether a particular swap occurred. Keep those results separate until their identifiers and recorded activity match.
What readers ask about Screener
Does an ordinary token transfer add to DEX swap volume?
An ordinary token transfer isn't itself a swap and shouldn't count as swap volume. Transfers can accompany trades, liquidity changes, or unrelated movements between addresses. Classifying activity requires the exchange operation and its execution context. Counting every transfer involving a pool would mix different operations into the trading total.
Why can a USD chart show a different percentage change from a quote-token chart?
A USD chart incorporates the dollar valuation of the quote token as well as the pair's exchange ratio. If that valuation changes, the dollar price can move differently from the price expressed in quote tokens. Comparing percentage changes requires matching the denomination, starting observation, and ending observation.
Are buy and sell counts the number of distinct traders?
Buy and sell counts measure classified trading activity, so they don't establish how many distinct people traded. One address can trade repeatedly, and one person can control several addresses. A separate count of participating addresses still measures addresses rather than verified human identities.
Will a longer candle interval recover trading history from before a pool existed?
A longer candle interval can't create trading history from before the selected pool existed. It groups the available observations into broader periods. Another pool containing the same token may have older activity, but that history belongs to a different market and needs its own identification.
Is a price calculated from a recorded swap an executable quote?
A price calculated from a recorded swap describes that completed exchange, rather than the terms of a new transaction. A new quote depends on the requested amount, available liquidity, applicable fees, and market state. Even an accurately indexed trade price doesn't establish the output that a later swap will receive.