← THE CHARTSPOD LEDGEROPEN TERMINAL →
DATA · POOL TRADES TIMING

GeckoTerminal Pool Trade Data: Event Time vs Retrieval Time

Pool trades carry a block timestamp — the event time. The default response is the last 300 trades in 24 hours, so busy pools truncate.

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

Short answer

CoinGecko's trades-by-pool endpoint returns trades with block_number, tx_hash, block_timestamp, kind (buy/sell), amounts and USD values; it's cacheless. By default it returns the last 300 trades in the past 24 hours; higher plans can page further and choose a 1d/7d/30d trading period. On a busy pool, 300 trades may cover minutes, not a day. Use block_timestamp as event time, record retrieval time, and check the time span actually covered.

Which times the data carries

TimePresent?Meaning
block_timestampYesEvent time
block_numberYesOrdering
Retrieval timeNoRecord it
CoverageLast 300 / 24 hMay truncate

See GeckoTerminal Pool Trade Data on live data in the free ChartsPod terminal.

Open the ChartsPod terminal

What to record yourself

Field to storeWhy
retrieved_atPolling reference
tx_hashDeduplication
block_timestampEvent time
kindBuy/sell
span coveredTruncation check
Pool Trades: a stored recordPool Trades: a stored record: retrieved_at — Polling reference; tx_hash — Deduplication; block_timestamp — Event time; kind — Buy/sell; span covered — Truncation check.retrieved_atPolling referencetx_hashDeduplicationblock_timestampEvent timekindBuy/sellspan coveredTruncation check
Every pool trades row carries its own clock. Original ChartsPod editorial graphic.

Example

Pool Trades: event vs retrieval (illustrative)Pool Trades: event vs retrieval (illustrative): RESPONSE: 300 trades; OLDEST: 11:42:10; NEWEST: 11:49:58; SPAN: 8 minutes, not 24 hours.RESPONSE300 tradesOLDEST11:42:10NEWEST11:49:58SPAN8 minutes, not 24 hours
Two clocks, one record. Original ChartsPod editorial graphic.

Illustrative: a delta computed from one response covers only eight minutes on a busy pool. Polling every few minutes and deduplicating by tx_hash builds a fuller record.

Related: GeckoTerminal New-Pool Data: Event Time vs Retrieval Time, GeckoTerminal for CVD Data Quality: What It Can and Cannot Cover.

Use block_timestamp as event time, record retrieval time, and check the time span actually covered.

Test GeckoTerminal Pool Trade Data on a perpetual chart; no account is needed to chart.

Launch ChartsPod

Questions readers ask

What timestamp do pool trades have?

block_timestamp.

How many trades are returned?

By default the last 300 in 24 hours.

How do I avoid duplicates?

Deduplicate by tx_hash.

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. CoinGecko API: Trades by pool address — last 300 trades in 24 h by default; block_timestamp; kind; cacheless.

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.