Dexscreener

Reference guides

Dexscreener alerts are above-or-below triggers for DEX pairs

Dexscreener alerts are price-threshold notifications attached to a specific decentralized-exchange pair. Choose an upper level to learn when the displayed quote moves above it, or a lower level to learn when the quote moves below it. The alert watches indexed market data and sends a notification; it does not place a swap, reserve liquidity, or guarantee an executable price. Pair selection therefore matters as much as the number entered, especially when one token trades across several pools.

Key takeaway: They are price-threshold notifications for DEX pairs that trigger when the quoted price moves above or below a user-selected level.

Place the first upper and lower boundary

A Dexscreener alert setup begins on the exact pair page, beside the Watchlist and Alerts controls. Open Alerts, read the reference unit printed in the form, choose above or below, enter the target, and save it. The current displayed value supplies context, while the number you enter becomes the boundary. No blockchain transaction is broadcast because the saved rule belongs to the monitoring service rather than the pool contract.

Two directions cover different decisions. An upper boundary marks a breakout, recovery level, or review point above the displayed quote; a lower boundary marks a pullback, range exit, or review point below it. Give each boundary one purpose, then remove it when that purpose ends. A crowded collection of nearby thresholds produces repeated notifications from ordinary back-and-forth trading and makes the important level harder to recognize.

The pair address decides which market is watched

A pair address selects one liquidity pool, not every market carrying the same ticker. WETH/USDC on Uniswap, WETH/USDT on Uniswap, and WETH/USDC on another exchange hold separate reserves and produce separate prices. Raydium and Orca likewise maintain distinct Solana pools for the same SPL token. Selecting by symbol alone leaves room for the alert to follow a pool other than the one used for analysis.

Address structure helps with the identity check. An Ethereum, Base, or Arbitrum address is 20 bytes and is normally rendered as 40 hexadecimal characters after the 0x prefix; a Solana public key is 32 bytes and is commonly displayed in Base58. The token contract or mint address identifies the asset, while the pair or pool address identifies the market. A saved threshold belongs with that market context.

How far should the threshold sit from the displayed quote?

Threshold spacing for Dexscreener alerts should match the decision horizon and the pair's normal movement. Percentage notation makes the distance portable across prices: 1% equals 100 basis points, 2.5% equals 250 basis points, 5% equals 500 basis points, and 10% equals 1,000 basis points. A tighter boundary reacts to smaller moves; a wider boundary ignores more noise before demanding attention.

Pool structure still changes what those percentages mean. Uniswap v3 defines widely used fee amounts of 0.01%, 0.05%, 0.3%, and 1%, but the chosen fee tier does not determine price impact. Trade size relative to active liquidity moves the pool price, so recent swap size and depth deserve more weight than the fee label. Thin Raydium or PancakeSwap pools cross close boundaries with fewer quote-asset units than deep pools.

Four chart windows for judging a boundary

The four DEX pair context windows - 5 minutes, 1 hour, 6 hours, and 24 hours - show whether a proposed boundary sits inside recent noise or beyond it. Read them before saving the level, because a movement that dominates the 5-minute panel could remain minor across 24 hours. The panels describe past change; the alert itself continues to test the chosen price condition.

TradingView Advanced Charts provide finer chart intervals ranging from 1 minute to 1 month. A short interval reveals individual bursts, while a longer interval preserves the larger range that motivated the alert. Changing the chart interval does not rewrite the stored target: the interval changes the picture, whereas the threshold remains a numeric boundary for that pair.

What makes an above-or-below condition true?

An above-or-below condition becomes true when the indexed value for the selected pair reaches the chosen side of the boundary. Dexscreener obtains its market data directly from the blockchains it tracks and processes raw logs with its own indexer. A swap changes pool state, the indexer parses that state change, and the displayed pair price updates. The rule compares that updated value with the saved target.

Automated market maker design explains why a single trade matters. A constant-product pool changes its reserve ratio after every swap, while concentrated-liquidity systems such as Uniswap v3 and Orca Whirlpools move through configured price ranges. In Uniswap v3, adjacent ticks represent a price ratio of 1.0001. A threshold crossing therefore reflects observed pool state, not a TradingView drawing, moving-average signal, or candle-close instruction.

Quote units change the meaning of the same number

The quote unit defines what the threshold measures. Pair pages show a USD estimate alongside the price denominated in the pool's quote asset, such as USDC or SOL; the unit printed in the alert form is therefore part of the rule. A JUP/SOL boundary and a JUP/USDC boundary respond to different ratios, even when both pages also display a converted USD value.

Token precision adds another layer without defining economic accuracy. USDC uses 6 decimal places on Ethereum and Solana, WETH uses 18 decimal places as an ERC-20 token, and 1 SOL divides into 1,000,000,000 lamports. These fixed units control on-chain representation. They do not promise that every displayed decimal has executable depth, so copy the intended unit and visible decimal position deliberately when entering a small threshold.

Notification delivery is a second state

A Dexscreener price alert has two separate states: the rule must be active, and the destination must be allowed to show notifications. Dexscreener publishes apps for iOS and Android and describes its price alerts as unlimited. That count concerns how many alerts the product permits; device permissions, focus modes, and operating-system notification settings still govern whether a message appears outside the open app.

Cross-device use needs a consistent signed-in identity and a quick visibility check in the Alerts screen. Confirm that the target, pair, direction, and unit appear on the phone that should receive the message, then review that app's notification permission. Seeing a threshold on a desktop screen proves the rule exists, while seeing it on the phone and allowing notifications establishes the delivery path.

A crossed line is an observation, not a fill

A crossed Dexscreener threshold records a market observation for one pair; it is not a limit order or swap receipt. Execution price also incorporates route selection, pool depth, trade size, fees, and slippage. Jupiter may route a Solana swap across several venues, while 1inch may compare EVM liquidity across pools, yet the original alert still describes only the selected market shown on its pair page.

In a shallow pool, one swap can carry the displayed price across a boundary and the next swap can move it back. Inspect the triggering trade and surrounding liquidity through the pair feed, Solscan, or Etherscan before treating the notification as a persistent move. The alert did its job when it reported the crossing; persistence, available depth, and the price for a specific order size are separate questions.

Where simple price thresholds stop

A simple price threshold answers one Boolean question: is this pair above or below the saved number? Volume surges, liquidity changes, multi-pool spreads, and indicator conditions require separate logic. Dexscreener filters help discover pairs that meet screening criteria, but a filter result is not a standing price notification. Keep the built-in alert for a clear boundary and use programmatic monitoring only when the condition genuinely needs additional fields.

The Dexscreener API supplies pair data for such monitors rather than hosting the custom rule. Published pair lookup endpoints allow 300 requests per minute, the token batch endpoint accepts up to 30 addresses in one request, and several profile or boost feeds allow 60 requests per minute. Code using those feeds must store its own thresholds, handle duplicate observations, and deliver its own messages. Dexscreener alerts remain the shorter route when above or below is the complete condition.

First published 28 Jul 2026