DEX screener
DEX screener helps check incomplete market data through chain and pair lookups
· updated
DEX screener supports address searches that help identify the intended pool when market data appears incomplete. Match the chain, token, and pair before interpreting a missing figure. Then distinguish an absent result from an unavailable field, a changed market value, or a comparison that uses different inputs.
A matching chain and pair address establish which market you're checking; missing price or liquidity still needs a separate explanation.
A different pool changes the comparison
Comparing different pools can make valid market data look inconsistent. A token search and a lookup for one selected pair answer different questions. The first helps locate markets containing an asset; the second concerns a particular pool. Keep that distinction visible when investigating an unexpected result.
A matching symbol alone doesn't settle whether two displays describe the same market. Compare their chain and addresses before deciding that either figure is wrong. Otherwise, a refresh may appear to fix the discrepancy simply because the selected pool changed. Record which pool each observation concerns, especially when several results share similar names.
Match the lookup to the address
Use an address lookup that corresponds to the object you already know: a token or a particular pair. Search accepts names, symbols, token addresses, and pair addresses.
For a known pool, the API supports lookup by chain and pair address. A separate lookup returns pools for a token address on a specified chain.
Treat the address type as part of the input. Pasting a token address into a field that expects a pair address doesn't establish that the pool is absent. If the address type is uncertain, resolve that uncertainty before repeating the request. Discovery filters also deserve a separate check: the criteria used to narrow a results list aren't evidence that a specific pool has disappeared.
What does a missing result or field mean?
A missing result leaves the pool unconfirmed through that lookup; a missing field leaves that measurement unavailable. Neither establishes a numeric zero.
No matching pair returned
An empty lookup leaves the intended market unconfirmed through that request. It doesn't, by itself, identify the cause. Keep the unresolved question narrow: whether the input identifies the intended pool and whether that lookup returns its record. Don't replace the missing result with a similarly named market just to obtain a chart.
The pair returns with incomplete figures
The API permits null values for USD price, liquidity, fully diluted valuation, and market capitalization. A recognizable pair record can therefore coexist with an unavailable measurement. Examine the particular field that your comparison requires.
An unavailable measurement
Preserve the gap in notes or exports. Substituting another pool's figure would change the observation's meaning, even when both pools contain the same token.
An explicit zero
Keep a returned zero distinct from an absent value. Check the field and period before interpreting it. A zero in one activity measure doesn't describe every aspect of the pool, and it shouldn't overwrite unrelated missing information.
Keep the same market and measurement window
A useful comparison holds the market identity, units, and observation period constant while examining the discrepancy.
Write down when each observation was taken. If one figure comes from an earlier view, a later difference doesn't necessarily establish a processing error. The same applies to activity measured over different periods. Pair identity supplies a durable reference for the comparison; prices, balances, and activity are changing observations. Comparing charts requires both pieces of context.
Reconcile those differences before choosing a preferred number. Avoid averaging incompatible observations or copying a visible price into an unavailable field. Either operation would hide the original gap. An unresolved comparison is more useful than a precise-looking figure assembled from mismatched inputs.
Wait only when another lookup can answer the question
Waiting is useful when the unresolved issue concerns data becoming available, while an input mismatch requires correction.
Automatic token listing requires a liquidity pool and at least one transaction. Those prerequisites don't supply a fixed waiting period for every missing field. Repeating a lookup doesn't create the underlying market activity or correct an address entered for the wrong object.
Before retrying, identify what could change the answer: corrected input, a recovered request, or newly available data. A successfully returned record with an absent measurement calls for different handling than a request that failed entirely. If nothing relevant has changed, repeated refreshes may only reproduce the same uncertainty.
Stop the comparison when it requires a value that remains unavailable. Other populated fields don't substitute for that particular measurement.
A matched pair with missing liquidity
A liquidity comparison can continue only when the intended pool has a usable liquidity observation. In this hypothetical example, the selected chain, token address, pair address, and returned field states are illustrative inputs. No live market or amount is implied.
In the normal case, the lookup returns the intended pool and a populated liquidity field. The reader records that value with the pool identity and observation time. That observation can now be compared with another observation for the same pool and units, although the value can change afterward.
In the incomplete case, the same identity matches, but the display shows liquidity as unavailable. The reader keeps liquidity marked as unavailable and checks whether the problem lies in the retrieved response or its presentation. If the response contains a value that the display omitted, the presentation needs correction. If the response itself contains null, a display adjustment can't recover the missing measurement.
After correcting a presentation problem, check the display against the retrieved response. Retry the lookup after correcting a retrieval problem or when checking whether new data is available. If liquidity then appears for the same pool, the reader records the new observation. If it remains absent, the comparison stops without assigning zero. The address match is the stable requirement; the returned liquidity value is the changing input.
Use transaction records when a chart cannot settle execution
Transaction status should be checked against the transaction record when the question is whether an operation completed.
A missing chart update leaves a display question unresolved. It isn't sufficient evidence that an operation failed, so it shouldn't trigger another submission by itself. Keep the transaction identifier separate from the token and pair addresses: each identifies a different object. A pair lookup is appropriate for checking market observations; a blockchain explorer or the originating application's transaction record addresses execution status more directly.
DEX screener FAQs
Should a saved value replace a field that is missing from a fresh lookup?
A saved value should remain labeled as an earlier observation. Keep its pool identity and observation time alongside it. Silently carrying it forward makes an incomplete fresh result look complete and conceals the gap. Historical data can support a comparison, provided the display distinguishes it from the latest retrieved result.
Does a failed API request mean that the pair has disappeared?
A failed request doesn't establish whether the pair exists. It establishes that the request didn't produce a usable answer. Keep request errors separate from successful responses that contain no matching record. This distinction prevents a connection or service problem from becoming an unsupported claim about the market.
Which details help explain a pair lookup discrepancy?
The most useful details identify the request and the exact disagreement. Include the chain, address type, selected pair, affected field, observation time, and any returned error. Note whether the discrepancy appears in the response itself or only in its display. Public market identifiers are sufficient; private keys and recovery phrases have no role in explaining missing chart data.
Is a screenshot enough to compare a missing value later?
A screenshot helps only when it preserves enough context to identify the observation. A cropped number without the pool identity, field label, units, or capture time can be ambiguous. Retain those details separately if they aren't visible. The image records what the display showed; it doesn't explain why a field was unavailable.
How should an export handle one incomplete pair among several results?
An export should preserve availability separately for each pair and field. Keep usable observations attached to their own market identifiers, and leave incomplete measurements marked as unavailable. Don't borrow another pair's liquidity or discard every record because one is incomplete. Any total that excludes missing values should clearly state that its coverage is partial.