DEX screener watchlists and price alerts for pair monitoring

Watchlists, alerts and chart views

Watchlists suit repeated visits to selected pairs, while price alerts suit a defined condition that deserves attention between visits. The mobile app includes both features alongside charts and on-chain trades.

The available views answer different monitoring questions. A saved collection helps retain your selection, while a chart shows movement through time. Transaction records add detail about the activity behind that movement. None of these views replaces the others.

The market behind a saved entry

A saved entry remains useful only while it identifies the market you mean to follow, especially when several pools contain the same token. Pair data distinguishes the network, exchange, token addresses and pair address. These identifiers provide continuity when names or displayed prices look similar.

Keep that identity attached to any monitoring notes. A comparison between visits loses meaning if it silently switches pools. Likewise, an alert associated with a different market cannot establish what happened in the chart you were watching. The address comparison belongs before threshold interpretation, rather than after an unexpected notification.

Price units behind a threshold

A numerical threshold needs a price unit, because a token's value in dollars and its value against the paired asset describe different relationships. Pair records can contain both dollar and native price fields.

The unit shown beside the alert condition should govern how you read its target. Do not copy a number from a different display basis without checking what it represents. A change in the quote asset's dollar value can also affect the relationship between those displays. Keeping the unit in your notes prevents a later chart comparison from changing the question that the alert was meant to answer.

A threshold tied to a reason for returning

A useful threshold marks a price at which you want to revisit the pair, rather than a number chosen solely to generate notifications. Write the reason in ordinary terms, such as reassessing the market at a previously identified level. No universal percentage or distance suits every monitoring task.

The saved condition matters more than an unsaved value in an input box. Before depending on an alert, inspect the condition that the application retained. Preserve its comparison direction where the interface specifies one. A target for an upward move and a target for a downward move answer different questions, even when the numerical level matches.

Chart intervals change the visible shape

A chart interval changes how trading history is grouped, so a short movement may look prominent at one scale and small at another. A candlestick records the opening, highest, lowest and closing prices within its interval.

The most recent candle may still be forming. Its shape can change as further trades arrive, which makes an unfinished candle different from a completed historical one.

Use matching intervals when comparing a chart before and after a notification. Changing the display interval reorganizes the history; it does not undo a recorded trade. It also does not establish that an alert uses candle closing prices. Interpret the alert through its own stated condition, rather than borrowing a rule from the chart's appearance.

Trading activity around the movement

Recent trades help establish whether a visible movement accompanied ongoing activity or a sparse set of transactions. Volume and transaction counts describe different aspects of that activity: traded amount and recorded events. Read them over matching periods before drawing a comparison.

A large volume figure does not establish how many independent participants traded. Repeated transactions can contribute to activity, and a count alone does not reveal their motivation. Compare the trades recorded around the notification with the movement on the selected chart. Pair screens provide period-based activity alongside price changes.

Liquidity around a price move

Liquidity gives a price notification market context because the effect of a trade depends partly on the liquidity available in its pool. A given trade can have greater price impact in a shallower pool.

A liquidity filter may have helped select the pair initially. That earlier selection does not freeze the pool's condition. Revisit liquidity when assessing a later price move, particularly when the market looks materially different from the original shortlist. This keeps ongoing monitoring connected to the reason the pair was selected without repeating the whole discovery process.

View image file

The alert price also cannot establish the average execution price of a proposed swap. An executable quote depends on the intended amount and available route. Monitoring can end with continued observation; receiving a notification creates no requirement to trade.

Quiet trading and incomplete displays

A quiet pair and an incomplete display can both look uneventful, but they support different conclusions. A numerical zero reports a value within the displayed scope. A blank field, loading message or unavailable value does not supply that same information.

Missing data should remain unknown. Treating an unavailable liquidity or price field as zero would introduce a value that the display has not established.

Recent transaction records can help distinguish inactivity from an isolated chart problem, although a partial display cannot prove that every component is current. Keep the diagnosis specific to what is visible. An unchanged last trade provides less evidence of continuing activity than newly recorded trades. Neither observation, by itself, explains whether a notification reached the device.

Why has a price alert not appeared on my phone?

A missing notification can reflect an unmet alert condition, a different monitored market or phone settings that suppress the notification. Silence alone does not identify which explanation applies.

Start with the alert's retained condition and the market it references. A chart from another pool, a different price unit or a later price observation may not demonstrate that the configured condition occurred. Avoid changing the target merely to compensate for an unexplained delivery problem.

On Android, app notifications can be disabled or silenced, and lock-screen presentation has separate controls. The available settings vary by device.

A visible notification confirms that a message appeared on that device. A silent phone does not prove that the market remained unchanged. Notification permissions and displayed market activity therefore deserve separate attention. Reinstalling software or changing several settings together can also make it harder to identify which condition caused the original problem.

Adjustments that preserve the monitoring question

A monitoring adjustment should address the specific mismatch you found, while leaving unrelated choices intact. A wrong market requires correcting the selection. An unsuitable price target calls for reconsidering the condition. If Android shows that notifications for DEX screener are disabled, enable them in the phone's app notification settings. Check that they remain enabled; this confirms the permission setting, not delivery of a future alert.

Changing several controls together obscures the effect of each change. Keep a brief note of the intended condition before revising it, especially when multiple alerts concern similarly named pairs. The relevant confirmation is the retained setting, not simply the disappearance of an editing screen. If the displayed condition still differs from the intended one, the adjustment remains incomplete.

The information to retain after an alert

After reviewing an alert, check that the remaining monitoring settings match the pair and price condition you intend to follow. Record the market identity, event time and price unit if the movement needs later comparison. Retain uncertainty where the available records do not explain it.

The notification's time and the time you opened the chart are different observations. Price may change between them, so a later display need not reproduce the notified value. Dismissing a message also tells you nothing about whether the alert remains configured. Inspect the alert's displayed state before assuming that monitoring continues.

Keep the comparison period explicit in any final note. A move over a short window and a change over the past 24 hours can coexist. The pair screen's 24H price-change figure describes the latter.