All chains
T

Tron

Other Layer 1

Tron is a blockchain network indexed by the SQD Network. Access real-time and historical data including blocks, transactions, and event logs through the SQD Portal API.

Quick Facts
Networks 1
Runtime Other
Real-time Yes
Data tables 0
Category Layer 1
Networks
1
Coverage
Real-time + archive
Start block
0 (genesis)
License
Open-source SDK

Networks

tron-mainnet
Real-time Other mainnet 0 tables

Tron on SQD

Validated at ingestion

Tron data is validated by SQD Network workers before it reaches the Portal. Validation is performed across the network rather than by a single ingestion node, so a faulty upstream source can't poison the dataset.

Decoded, schema-typed

Tron data served as decoded, schema-typed tables, ready to query. Your indexer queries the data directly.

Archive plus real-time

Single Portal endpoint serves Tron from genesis through the current head, with sub-second hot-path latency. No separate streaming pipeline to wire up.

Open-source SDK

The Pipes SDK is open-source. Connectors for Postgres, ClickHouse, MongoDB, SQLite and Parquet, plus a custom-target hook. Run your Tron pipeline on your own infrastructure pointing at the SQD Portal.

Build with Tron data

Common production patterns teams build with SQD on Tron.

Stream Tron data in two lines

Example below uses the public Tron endpoint, free for development. For full SDK reference, see the documentation.

curl --compressed -X POST \
'https://portal.sqd.dev/datasets/tron-mainnet/stream' \
-H 'Content-Type: application/json' \
-d '{
"type": "evm",
"fromBlock": 0,
"toBlock": 100,
"fields": {
"block": {"number":true,"timestamp":true},
"transaction": {
"hash": true,
"from": true,
"to": true,
"value": true
}
},
"transactions": [{}]
}'
tron-mainnet/stream
EVM · blocks 0100

Frequently asked questions

How does SQD compare to pulling Tron data from its own API?
Pulling Tron data from its native API means polling, handling rate limits, persisting raw responses, and managing reorgs or replays yourself. SQD pre-indexes Tron into decoded, schema-typed tables (blocks, transactions, logs) served as a single streaming endpoint, with full historical depth and the same access pattern you would use for any other chain on SQD.
What does SQD cost for Tron data?
The public Portal endpoint at portal.sqd.dev/datasets/tron-mainnet is free for development. Production workloads run on the SQD Portal with tiered pricing based on the network and request volume. See the pricing page for current tiers, or contact us for an enterprise quote.
Can I self-host SQD's Tron indexer?
Yes. The Pipes SDK is open-source. You can run a Tron pipeline on your own infrastructure pointing at the SQD Portal.
Can I export Tron data to a data warehouse or pipeline?
Yes. The Pipes SDK streams Tron data from the Portal into Postgres, ClickHouse, MongoDB, SQLite, Parquet, or a custom target you implement. See the SDK docs for the connector reference.
Does SQD validate Tron data?
Tron data ingested into SQD is validated and signed by SQD Network workers before it reaches the Portal. Validation is performed across the network, not by a single ingestion process, so a faulty upstream source can't poison the dataset.
Does SQD support real-time Tron data?
Yes. Tron is served with both real-time and historical data from the same Portal endpoint, with sub-second latency on the hot path. No separate streaming pipeline to wire up.

Learn more

Start building with Tron

Access Tron data through the SQD Portal, free tier available.