SELECT creator,
count() AS launches
FROM pumpfun_token_creation
GROUP BY creator
ORDER BY launches DESC
Decoded events → Typed tables → Your research
Ask a question of the data.
Query decoded Solana DEX activity with ClickHouse SQL. Explore swaps, token launches, migrations and wallet flows without building a transaction decoder.
Launch and creator research
Compare launch cohorts, creator activity and migration rates across a defined historical window.
Pool and fee reconciliation
Query reserve changes and individual fee components in decoded tables.
Wallet and funding analysis
Combine transfers with swap activity. Build your own wallet-level calculations in SQL.
Routed flow and microstructure
Use parent_program to study routed activity, and join arrival timing for recent sub-slot research.
Query with SQL.
Direct ClickHouse access supports joins, CTEs and window functions. Bring an existing query workflow, or ask us to turn a recurring query into a custom REST endpoint.
Decoded activity
Protocol events become typed columns.
ClickHouse tables
Confirmed data, organized for analytical queries.
Your application
SQL directly, or a separately scoped REST / ETL integration.
creators.sql / default
SELECT
replaceAll(toString(creator), '\0', '')
AS creator,
count() AS launches,
sum(bundled_buys) / 1e9
AS bundled_buys_sol
FROM pumpfun_token_creation
WHERE block_time >= now() - INTERVAL 1 DAY
GROUP BY creator
HAVING launches >= 5
ORDER BY launches DESCLIMIT 25
Example SQL
Ask a specific questionWhich creators launched at least five tokens in the last day? This query ranks them by launch count.
Respect schema conventionsOlder fixed-width values carry null padding. Strip it before grouping or comparing. SOL amounts use lamports; / 1e9 converts to SOL.
Keep the window boundedUse each table's date or partition column. Large swap tables need a partition filter in PREWHERE.
Building a reaction loop? The indexer is an analytical database, with rows queryable about 15 seconds after block confirmation. For live event subscriptions, explore Solana gRPC streaming.
Coverage, history and limits.
From launch to liquidity.
Typed columns. Queryable events.
Follow the lifecycle of a token, reconstruct pool activity or study a wallet across protocols. Coverage is explicit: each protocol has its own tables and columns.
The earliest table starts on 17 January 2024. Other tables keep a rolling window. Check retention before planning a backtest or a long-running data pipeline.
Rows become queryable approximately 15 seconds after block confirmation. Query runtime depends on the workload.
Timing within a slot
tx_timestamps.entry_timestamp records arrival at our Amsterdam shred receiver. Join on (slot, tx_idx) or signature. It has 14-day retention.
Receiver arrival timestamps. Timestamps have nanosecond resolution and microsecond-level real-world variance. Use them to study arrival at the receiver; transaction creation and end-to-end delivery require separate measurements. A missing timing row means the receiver did not observe that shred. Read the timing model ↗
Price & access.
Solana
Historical Data Indexer
Separate subscription
Decoded Solana DEX activity through ClickHouse SQL.
Full documented schema access
Direct ClickHouse SQL queries
No per-request fees; agreed usage limits apply
Custom REST and Python ETL quoted separately
$300
/ month
Free trial up to 24h on request, no card; our team confirms availability and setup. Crypto-only, prepaid subscriptions.
January 2024 is the start date for pumpfun_token_creation, the deepest table. Retention varies by table, from 14 days through full history. Some columns were introduced later and older rows contain type defaults. Check the table reference for your exact study.
Is this a live transaction stream?
The indexer stores decoded data for SQL analysis, with rows queryable about 15 seconds after block confirmation. Choose gRPC streaming for live event subscriptions, or RPC for node requests.
Can you provide a REST API for my query?
Yes, custom REST endpoints wrap a specific recurring query. Start in the portal with the tables, filters, aggregation and expected request volume. Custom REST and Python ETL work are quoted per scope on top of the base subscription.
Are amounts already adjusted for token decimals?
Amounts use raw base units: lamports for SOL and each mint's base unit for tokens. Apply token decimals in your calculations and interpret fee-rate fields in basis points.
What should I confirm before a long backtest?
Check each table's retention, populated-since dates for columns, partition keys and raw units. For sub-slot work, timing observations are receiver-specific and only kept for 14 days. Arrange extended retention or an export with the team in advance.
Is access immediate after opening the portal?
Our team reviews access and trial requests manually, then provides your connection credentials. If you need help planning the workload, contact Telegram support.