TRON

Six Parquet tables with 251 documented columns in total: blocks (13), transactions (36), calls (46), events (45), transfers (43) and dex_trades (68). Each purchase covers the window you choose, through to yesterday, refreshed daily. The Full tier starts at the start of indexed history on 25 June 2018.

To 25 June 2018, the start of indexed history; the first transfer sits at block 342. TRON's shape has changed since: USDT moved from Omni onto TRC-20 in 2019, and stablecoin volume has grown until it dominates the chain. A baseline before those shifts, a long backtest, or a contract's deployment-to-present history needs the full archive rather than a recent slice.

Transfers alone is about 13 billion rows, estimated from the live table for the TRON Transfers product. We size the other tables before delivery and send you the exact figures with the manifest, so you can plan storage before downloading. If calls and events are more than you need, we can quote the other four tables on their own.

On Transaction_Hash, which appears in every table except blocks; blocks join on Block_Number. Within a transaction, Call_Index orders the call frames, Log_Index orders the logs, Transfer_Index orders the transfers and Trade_Index orders the swaps.

Balance updates. The chain-wide balance_updates_address table exists in our store but is not part of this bundle, because it carries several rows per transfer and would dominate the size. If you need it, ask and we will quote it alongside this one.

The way TRON charges them. A transaction consumes bandwidth and, for contract calls, energy; what the sender's staked resources do not cover is burnt as TRX. Transaction_Receipt_EnergyUsageTotal and Transaction_Receipt_NetUsage are the resources used, Transaction_Receipt_EnergyFee and Transaction_Receipt_NetFee are the TRX actually burnt, and Transaction_Fee is their sum. Transaction_FeeLimit is the ceiling the sender set. In the sample window most transactions burnt nothing, because staked resources covered them.

Transaction_Result_Status is the chain's own outcome, spelt SUCESS or FAILED as the chain spells it. Transaction_Receipt_Result is the receipt code: DEFAULT for plain transfers and resource operations, SUCCESS or a failure reason such as OUT_OF_ENERGY for contract calls. Contract_Type and Contract_TypeUrl say what kind of operation the transaction was: TransferContract, TriggerSmartContract, DelegateResourceContract and so on.

Every venue we decode on TRON, identified by Trade_Dex_ProtocolFamily and Trade_Dex_ProtocolName on each row. In the sample window the only family present was SunSwap, which carries most TRON swap volume. Filter the family column to keep or drop a venue.

TRX and TRC-20 tokens with an hourly price series are valued; TRC-10 tokens and unpriced tokens carry 0. A USD value of 0 therefore means either a zero-value row or no price, and the column cannot tell the two apart. USDT is priced throughout, and it is the bulk of TRON transfer value.

Yes, throughout, and the export applies no filter of its own. Transaction_Result_Status and Transaction_Receipt_Result carry the chain's own result codes on every transaction, and dex_trades additionally carries Trade_Success. Spam tokens, zero-value rows and lookalike contracts are all kept too; the columns let you drop what you do not want.

Filter Call_To in calls and Log_SmartContract in events to the contract, in base58. For token flow, filter Transfer_Currency_SmartContract in transfers; USDT is TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t. Join on contract addresses rather than symbols, which repeat.

Amounts are decimal-adjusted decimal strings, carrying exactly as many places as the token has decimals; TRX amounts are adjusted from SUN, where one TRX is a million SUN, except the energy fee, which the chain reports in SUN. Multiply by ten to the power of the decimals for the raw on-chain 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 blocks 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.