Tron RPC node & Wallet API — chain ID 728126428

Last updated: November 1, 2026

Get API key Read the documentation

Network details

curl https://triport.io/public/tron \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'
# -> {"jsonrpc":"2.0","id":1,"result":"0x2b6653dc"}

What works today

Two surfaces, and which one to use

The EVM surface is the one your existing tooling already speaks: balances, code and storage, blocks, calls and logs, addressed as 0x hex. The native wallet surface is where Tron's own concepts live — account state and staked resources (getaccount), energy prices, chain parameters, witnesses, contract info, and triggerconstantcontract for a call that is executed but never sent. Most integrations need both: EVM for portable reads, wallet HTTP for anything Tron-specific.

getaccountresource (remaining energy and bandwidth) is not served today. For native request formats, see the Tron wallet API reference.

Address formats are the most common failure

The wallet surface accepts base58 addresses only with visible=true, and its hex form carries the 41 prefix, while the EVM surface expects 0x hex. A request with the wrong format usually returns an empty object rather than an error — which is not proof that the account does not exist. Check the format before concluding anything about the account, and see the wallet reference.

What teams run on it

These are supported workload patterns, with configured budgets rather than measured throughput promises.

• Monitor USDT deposits with eth_getLogs filtered to the USDT contract and its Transfer event, in windows of at most 100 blocks. Use the heavy budget, deduplicate logs, and inspect receipts. See scan USDT transfer history.
• Read TRC-20 balances with eth_call and balanceOf(address), on the ordinary read budget. Encode the holder as a 20-byte ABI address, without TRON's 41 prefix.
• Estimate before signing: triggerconstantcontract supplies energy_used;getchainparameters supplies the burn prices. Read about energy and bandwidth and estimate a USDT transfer fee.

Planning example: at TRON's nominal 3-second block interval, a day is 86,400 / 3 = 28,800 blocks. At 100 blocks per request that is 288 windows. Basic's configured 5 heavy requests/second gives 288 / 5 = 57.6 seconds (about 58 seconds) of request-budget time. This excludes network time, retries, receipt reads and competing calls; it is not a backfill benchmark. Block interval: TRON consensus documentation, checked 2026-10-25; budgets: TRON limits.

Historical blocks do not prove historical state

Tron's state profile here is latest-oriented. Fetching an old block succeeds, but a state read at that height may not — so a working eth_getBlockByNumber on an old block is not evidence that eth_getBalance or eth_getStorageAt will answer for the same height. Treat deep state reads as unsupported unless you have verified the exact range you need.

Terms on this page: TRC-20 · Super representative · Solidified block.

Limits and plans

2× burst buffer, included. Finite request-rate limits show sustained RPS and short burst capacity. A full buffer at 20 RPS can absorb up to 40 requests at once and refills at 20 requests per second. There is no quota on the number of bursts and no extra charge for them. Size ongoing traffic to sustained RPS. Categories with no per-category cap have no numeric burst ceiling. How burst capacity works.

The heavy budget is much smaller than the ordinary read budget on Tron — eth_getLogs and heavy wallet calls draw on it, so log backfills should be paced against 2/5/20/80 rather than the headline read rate. Plans: Basic $20, Pro $249, Business $499, Enterprise from $999 per month; Free is a 7-day trial with a single key in the EU region. See Tron limits.

Every plan with its limits on every network, and what a plan costs at its cap: RPC pricing.

Quickstart

# EVM read
curl https://triport.io/rpc/tron \
  -H "x-token: $TRIPORT_API_KEY" -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

# Native wallet read (base58 needs visible=true)
curl https://triport.io/rpc/tron/wallet/getaccount \
  -H "x-token: $TRIPORT_API_KEY" -H 'Content-Type: application/json' \
  -d '{"address":"TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t","visible":true}'

Tron EVM read methods

• eth_blockNumber
• eth_call
• eth_chainId
• eth_gasPrice
• eth_getBalance
• eth_getBlockByNumber
• eth_getCode
• eth_getStorageAt
• eth_syncing
• net_version
• web3_clientVersion