TriportRPCDashboard

EVM network documentation

Tron RPC API reference

MainnetChain ID 72812642812 RPC methods

Tron mainnet RPC endpoint: https://triport.io/rpc/tron (HTTPS), chain ID 728126428. Requests need a Triport API key in the x-token header; the Free plan is a 7-day trial. Endpoint, plans and limits: Tron RPC endpoint.

HTTPS endpointhttps://triport.io/rpc/tron
Tron RPC endpointPlans, endpoints & pricing for TronTron chain ID, RPC URL & network configIdentifiers with sources, wallet setupBest Tron RPC providers comparedPrices, rate limits and features, each with its source
All Tron reference pages 28

JSON-RPC · tron read rpc

JSON-RPC · tron read rpc heavy

Guides & operations

Contracts

Capabilities

  • EVM JSON-RPC readsAvailableFree+EVM hex addresses differ from native; state profile is latest-oriented; historical blocks do not prove old state.
  • eth_getLogsAvailableFree+
  • Native wallet HTTP (read)AvailableFree+Base58 needs visible=true, hex addresses use the 41 prefix; an empty object after a wrong address is not proof of a missing account; no submission.

Statuses reflect checks up to 2026-09-16. Rate limits are plan policy, not measured capacity.

TRON's read-only API has 12 JSON-RPC methods (11 standard reads plus eth_getLogs) and 12 native wallet HTTP methods. JSON-RPC uses EVM hex quantities; wallet block numbers are decimal JSON numbers. Wallet addresses default to hex-41; Base58 requires visible=true. Connection values, plans and the read-only boundary: Tron RPC node endpoint. Native HTTP calls: Tron wallet API.

Method / EndpointNetworkChain IDAuthenticationRequired scopeTier / rate limit
POST https://triport.io/rpc/tronTron mainnet728126428x-token: $TRIPORT_API_KEYtron:rpcCategory-specific RPS; see Limits

Endpoints

SurfaceEndpointReference
HTTPShttps://triport.io/rpc/tronBackend path /rpc/tron
RESTProduct routesContract: docs/api/product-rest/tron.yaml

Quickstart

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":[]}'

What's available

12 JSON-RPC methods in the OpenRPC catalog:

  • tron_read_rpc: 11
  • tron_read_rpc_heavy: 1

The wallet API documents account state, chain parameters, energy prices and local contract simulation. Remaining energy and bandwidth (getaccountresource), estimateenergy, transaction submission and /walletsolidity are not served. Historical block availability does not establish historical account-state availability.

Limits

See network limits and Rate Limits & Tiers.

Finite request-rate budgets include a 2× burst buffer at no extra cost. It refills at sustained RPS; there is no quota on the number of bursts. Interval categories use seconds and have no RPS burst. See Burst capacity.

CategoryFreeBasicProBusinessEnterprise
tron_read_rpc15 RPS sustained · up to 30 burst20 RPS sustained · up to 40 burst100 RPS sustained · up to 200 burst250 RPS sustained · up to 500 burstunlimited
tron_read_rpc_heavy2 RPS sustained · up to 4 burst5 RPS sustained · up to 10 burst20 RPS sustained · up to 40 burst80 RPS sustained · up to 160 burstunlimited

eth_getLogs accepts at most 100 blocks and shares tron_read_rpc_heavy with getblockbynum and triggerconstantcontract. All other published reads use tron_read_rpc. These are configured limits, not measured node capacity.

Errors

See network-specific errors and the shared error reference.

Methods

tron read rpc (11)

tron read rpc heavy (1)

Streams

No mounted stream is published for this network.

JavaScript (fetch)

The same request from JavaScript (Node 18+ or the browser):

const res = await fetch("https://triport.io/rpc/tron", {
  method: "POST",
  headers: {
    "x-token": process.env.TRIPORT_API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}),
});
const { result } = await res.json();
console.log(result);