Solana

Seven Parquet tables with 300 documented columns in total: blocks (9), transactions (17), transfers (47), dex_trades (82), dex_pools (64), dex_orders (63) and rewards (18). Each purchase covers the window you choose, 1, 6 or 12 months, through to yesterday, refreshed daily.

Because we hold row-level Solana data, meaning individual transactions, transfers, swaps and orders, for the last twelve months on a rolling basis. Aggregated series such as per-token OHLCV go back further and are sold separately. The 12-month tier is therefore the deepest window we can deliver at this grain, and we would rather say so than sell a longer label.

Large. In the sample window Solana carried about 1,100 transactions and 700 transfers per slot, at roughly two and a half slots a second, and the DEX tables add one row per swap and per pool change. We size it per table before delivery and send you the exact figures with the manifest. If you need only the DEX tables, the Solana DEX Trades and Pools dataset is the same two tables at a lower price.

On Transaction_Signature, which appears in every table except blocks and rewards; those two join on Block_Slot. Within a transaction, Transfer_Index, Trade_Index and OrderEvent_Index order the rows, and the Instruction_CallPath columns say which program invocation each row came from.

Two things. Balance updates, the per-account pre and post balances for every transaction, exist in our store but are not in this bundle, because they run to several rows per transfer and would dominate the size. Raw instructions are also not a table here. If you need either, ask and we will quote them alongside this one.

A slot is a scheduled chance to produce a block, and some slots pass with no block. Block_Slot is the slot, Block_Height counts only blocks actually produced, and Block_ParentSlot shows the gap when slots were skipped. Files are cut by slot range, 50 slots per file, so a file can hold fewer than 50 blocks.

The owner. On Solana a token is held in a token account owned by a wallet, and most people mean the wallet. Transfers carry both: Transfer_Sender_Address and Transfer_Receiver_Address are the token accounts, Transfer_Sender_Token_Owner and Transfer_Receiver_Token_Owner are the wallets. For SOL itself the two coincide.

All programs we decode, identified by the ProtocolFamily and ProgramAddress columns on every row. In the sample window dex_trades held Pumpswap, Meteora, Raydium, Jupiter, Pump.fun, Orca Whirlpool, PancakeSwap and SolFi among others, and dex_orders held Magic Eden order events. The set grows as new programs are indexed; nothing is pinned to a fixed venue list.

What the chain attaches to each block. Every block carries the leader's fee reward, which is what the sample window shows; blocks at epoch boundaries also carry staking and voting rewards, and rent rewards where they occur. Reward_RewardType says which, and Reward_Commission is the validator's cut on the staking and voting kinds.

Swaps are priced from the safer side, so nearly every trade with SOL or a stablecoin on one side carries a value, and the token side's PriceInUSD is derived through it. Transfers and rewards are valued only for tokens with an hourly price series. A USD value of 0 means either a zero-value row or no price; the column cannot tell the two apart.

Yes. Transaction_Result_Success carries the outcome on every table that has it, and Transaction_Result_ErrorMessage carries the runtime's error text when it failed. The export applies no filter of its own, so vote transactions, spam tokens and zero-value rows are all kept; the columns let you drop what you do not want.

Filter Trade_Dex_ProgramAddress in dex_trades, Pool_Dex_ProgramAddress in dex_pools or OrderEvent_Dex_ProgramAddress in dex_orders to the program, base58. For a token, filter the MintAddress columns: Transfer_Currency_MintAddress in transfers, and the Buy or Sell currency mint in dex_trades. Join on mint addresses rather than symbols, which repeat.

Amounts are decimal-adjusted decimal strings, carrying exactly as many places as the token has decimals; SOL is adjusted from lamports, where one SOL is a billion lamports. Multiply by ten to the power of the decimals for the raw integer. Casting to float loses precision on large values. Booleans are the strings true and false.

One line in DuckDB: SELECT * FROM read_parquet('transfers/*.parquet') LIMIT 10. Pandas works too: pandas.read_parquet(path). The sample files open without credentials.

As flat Parquet named by block range, 50 slots per file and sorted ascending, one prefix per table, with a JSON manifest listing every file and its sha256. We prepare the files within 7 business days of purchase and email you the location. You choose at checkout where to collect them: a Requester Pays S3 bucket, downloaded with your own AWS account, or a Cloudflare R2 bucket with a read-only API key and no egress fees. Files stay available for 7 days from delivery. Enterprise orders can be delivered into your own S3, GCS or R2 bucket. Refreshed daily with T+1 latency, so a purchase made today includes everything to yesterday.

Yes. Each table links to a public sample file with real records, and the sample bucket holds full Parquet files you can load directly. No email address required.