Tron

TVM Layer 1

Tron is a high-throughput Layer 1 and the dominant settlement network for USDT (TRC-20). Its TVM is EVM-compatible, so contracts emit the same event topic signatures as Ethereum. SQD indexes Tron blocks, transactions, TVM event logs, and internal transactions, with filters for native TRX transfers, TRC-10 assets, and TriggerSmartContract calls.

Website Explorer

Quick Facts

Networks 1

Runtime TVM

Real-time Yes

Data tables 0

Category Layer 1

Networks: 1
Runtime: TVM
Coverage: Real-time + archive
Start block: 0 (genesis)
License: Open-source SDK

Networks

tron-mainnet

Real-time TVM 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

Both the Squid SDK and the Pipes SDK are open-source. Connectors for Postgres, ClickHouse, MongoDB, SQLite and Parquet, plus a custom-target hook. Run your Tron indexer on your own infrastructure or on SQD Cloud.

Build with Tron data

Common production patterns teams build with SQD on Tron.

DeFi & Trading

Index swaps, liquidations, and positions on Tron in real time.

Analytics

Build dashboards and metrics from full Tron historical state.

AI Agents

Give agents structured, decoded Tron data with the MCP server.

Wallets & Payments

Power balance, transfer, and history views for Tron wallets.

Compliance & KYT

Validated Tron data for transaction monitoring and audits.

Stablecoins

Track every mint, burn, and transfer of Tron stablecoins.

Real-World Assets

Auditable Tron data for tokenized RWA issuance and transfers.

Stream Tron data in two lines

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

1curl --compressed -X POST \
'https://portal.sqd.dev/datasets/tron-mainnet/stream' \
-H 'Content-Type: application/json' \
-d '{
    "type": "tron",
    "fromBlock": 0,
    "toBlock": 2,
    "fields": {
      "block": {"number":true,"timestamp":true},
      "transaction": {"hash":true,"type":true,"fee":true}
    },
    "transactions": [{}]
  }'

tron-mainnet/stream

TVM · blocks 0–2

Frequently asked questions

How does SQD compare to running a Tron RPC node?

A Tron RPC node serves raw bytes for recent state and rate-limits per request. SQD's Portal pre-indexes the full Tron archive into decoded, schema-typed tables (blocks, transactions, logs) and serves them as a single streaming endpoint. You skip the multi-day node sync, archive storage, monitoring, and scale-out work, and pay only for the data you stream.

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.

How is SQD's Tron data different from Tronscan?

Block explorers are read-optimized for human browsing of single blocks or addresses. SQD is built for programmatic indexing: stream millions of Tron blocks into your own database, run analytical queries across the full history, and back production applications with decoded data. Output is structured tables, not HTML pages, and there are no per-call rate limits geared toward UI traffic. If you wanted to build your own Tron explorer, the SQD Portal is what you would back it with.

Can I self-host SQD's Tron indexer?

Yes. Both the Squid SDK and the Pipes SDK are open-source. You can run a Tron indexer on your own infrastructure pointing at the SQD Network or the Portal. SQD Cloud also offers managed hosting if you'd rather not operate it yourself.

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?

Every Tron block ingested into SQD is validated by the SQD Network workers (hash chain, parent reference, and where applicable finality) before it reaches the Portal. Validation is performed across the network, not by a single ingestion process, so a faulty upstream node 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

What is a Tron indexer? → Tron's TVM emits the same event topics as Ethereum, so decoding is identical, but the request type, the typed-transaction schema, and the energy and bandwidth model differ. The data model, a real TRC-20 query, and what carries over from EVM. USDT on Tron: querying the largest stablecoin rail → Tron settles more USDT than any other chain. Pull TRC-20 USDT transfers from the Portal in one declarative query, read a real transfer end to end, and see why the energy and bandwidth model lets transfers settle without burning TRX. TRC-20 vs ERC-20: one token standard, two chains → TRC-20 mirrors ERC-20: the same Transfer event, the same topic0 hash, so a decoder built for one reads the other unchanged. What actually differs is the chain envelope: address format, native token, fees, finality, and how you fetch the data.

Start building with Tron

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

Try the Portal Read Docs