← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · DEX SCREENER PAIR DATA TIMING

DEX Screener Pair Data: Event Time vs Retrieval Time

A DEX Screener pair object describes a pool right now, but it doesn't say when 'now' was. Rolling windows like h1 volume end at the moment you fetched it.

By ChartsPod Editorial Team · Reviewed by ChartsPod Research
Published · Updated · 5 min read

Short answer

DEX Screener's documented Pair schema includes pairCreatedAt (nullable) but no updated-at or retrieval timestamp. Fields like priceUsd, txns.h1 and volume.h1 are rolling values as of the response. So the event time of the data isn't in the response: record your own retrieval time with every pair object. Two fetches a minute apart can show different h1 volumes because the window moved, not because of a new trade.

Which times the data carries

TimePresent?Meaning
pairCreatedAtYes (nullable)When the pair was created
Retrieval timeNoRecord it yourself
Window end (h1, h24)ImplicitTime of the response
Last trade timeNot in documented schemaInfer cautiously

Check DEX Screener Pair Data against a live market before relying on it.

Try it in ChartsPod

What to record yourself

Field to storeWhy
retrieved_at (UTC)Defines window ends
pairAddress + chainIdIdentity
priceUsd / priceNativeSnapshot price
volume.h1 / h24Rolling values
pairCreatedAtPool age
Dex Screener Pair Data: a stored recordDex Screener Pair Data: a stored record: retrieved_at (UTC) — Defines window ends; pairAddress + chainId — Identity; priceUsd / priceNative — Snapshot price; volume.h1 / h24 — Rolling values; pairCreatedAt — Pool age.retrieved_at (UTC)Defines window endspairAddress + chainIdIdentitypriceUsd / priceNativeSnapshot pricevolume.h1 / h24Rolling valuespairCreatedAtPool age
Every dex screener pair data row carries its own clock. Original ChartsPod editorial graphic.

Example

Dex Screener Pair Data: event vs retrieval (illustrative)Dex Screener Pair Data: event vs retrieval (illustrative): 14:00:00: Fetch #1: h1 volume $82k; 14:01:00: Fetch #2: h1 volume $79k; CAUSE: A big 13:00 trade left the window; STORE: Both with retrieved_at.14:00:00Fetch #1: h1 volume $82k14:01:00Fetch #2: h1 volume $79kCAUSEA big 13:00 trade left thewindowSTOREBoth with retrieved_at
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: h1 volume fell $3,000 between two fetches with no new trades; a large trade from 13:00:30 had rolled out of the one-hour window.

Related: DEX Screener Token-Pool Data: Event Time vs Retrieval Time, DEX Screener Search Results: Event Time vs Retrieval Time.

Two fetches a minute apart can show different h1 volumes because the window moved, not because of a new trade.

Compare DEX Screener Pair Data across Binance, Bybit, OKX and Hyperliquid markets.

Open markets in ChartsPod

Questions readers ask

Does DEX Screener say when data was retrieved?

Not in the documented schema; record it yourself.

What is pairCreatedAt?

When the pair was created (nullable).

Why did h1 volume change without trades?

The rolling window moved.

Sources and methodology

Field definitions come from DEX Screener's API reference and CoinGecko's onchain API documentation, read 17 October 2026. Where a schema doesn't document a timestamp, this guide says so and recommends recording retrieval time yourself.

  1. DEX Screener API reference — documented schemas: pairCreatedAt nullable; no updatedAt or retrieval-time field; 60 requests/min on several endpoints.

This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.

CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.