tronorb.com

TRON RPC endpoints

Public TRON mainnet endpoints for the java-tron HTTP API and JSON-RPC, tested live: latency and how far behind each node is.

Updated

EndpointHTTP APIJSON-RPCBlocks behind
TronGridhttps://api.trongrid.ioOfficial (TRON DAO). Free API key raises rate limits (TRON-PRO-API-KEY header).443 ms300 ms/jsonrpc0
PublicNodehttps://tron-rpc.publicnode.comNo sign-up.152 ms52 ms/jsonrpc1
dRPChttps://tron.drpc.orgFree tier answers JSON-RPC; the java-tron HTTP API needs a paid plan (as returned by the endpoint).—no answer—

Measured from Cloudflare’s edge on page load; latency from your location will differ. We list endpoints that answer without an account; providers that need an API key are not tested.

Quick test

curl -X POST https://api.trongrid.io/wallet/getnowblock

curl https://api.trongrid.io/jsonrpc \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_blockNumber","params":[]}'

More for developers

TRON RPC FAQ

What is the TRON RPC URL?

The official public endpoint is TronGrid: https://api.trongrid.io for the java-tron HTTP API and https://api.trongrid.io/jsonrpc for Ethereum-compatible JSON-RPC. Add a free TronGrid API key for higher limits.

Does TRON support Ethereum JSON-RPC?

Partly. java-tron exposes an eth_* JSON-RPC interface for reading chain data and calling contracts, but transactions are built and signed the TRON way — use TronWeb or the HTTP API to send them.

HTTP API or JSON-RPC — which should I use?

The HTTP API (/wallet/*) covers everything TRON-specific: resources, staking, TRC-10, account permissions. JSON-RPC is convenient for EVM tooling that only needs to read blocks, logs and contract state.

How are these numbers measured?

Each endpoint is asked for its newest block (getnowblock / eth_blockNumber) from Cloudflare’s edge when this page renders. “Blocks behind” compares it with the best head we saw. Figures are cached for about a minute.