What is the Tron API URL?

The Tron Mainnet endpoint with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io and use the standard full-node routes under it.

Does TronWeb work with BoltRPC?

Yes. Set fullHost to your BoltRPC endpoint when constructing TronWeb and every SDK call works unchanged. Existing TronGrid integrations migrate by swapping that one URL.

Is Tron EVM compatible?

Partially. Tron runs the TVM, a Solidity-derived virtual machine, but the chain has its own API, its own base58 address format and its own resource model. Use TronWeb rather than ethers.js or MetaMask.

How do fees work on Tron?

Tron uses bandwidth and energy instead of a simple gas price. Accounts get free daily bandwidth. Staking TRX earns bandwidth and energy; unstaked usage burns TRX.

Why is Tron important for stablecoins?

More USDT settles on Tron than on any other network. Low fees and three-second blocks made it the default rail for exchange transfers, remittances and merchant payments.

Why do public Tron endpoints fail in production?

Public Tron APIs apply strict per-key and per-IP rate limits that deposit scanners hit quickly. A dedicated endpoint removes those ceilings.

Does BoltRPC support WebSocket for Tron?

Yes, for new blocks. The Tron full-node API is HTTP, so the endpoint synthesizes a newHeads stream over WebSocket at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/tron: one message per block, every three seconds, 3 request units each. Subscribe, then fetch the block with /wallet/getblockbynum and scan it for the transfers you care about.

Can I use ethers.js or viem with Tron?

Yes, for reads. Tron's EVM-compatible JSON-RPC is served at https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron/jsonrpc with chain ID 728126428 (0x2b6653dc). ethers.js, viem and web3.js can query blocks, balances, logs and TRC-20 contracts through it. For signing and broadcasting transactions use TronWeb, which handles Tron's own address and transaction format.

Tron RPC Endpoint

Tron settles more USDT than any other chain. Get a dedicated full-node endpoint for deposit detection, broadcasts and TronWeb integrations.

chain id · 728126428HTTP APINative gRPCSynthetic WS

Start free trial Contact sales

LIVE LATENCY

47ms

LIVE

gateway round-trip · sampled every second

IN PRODUCTION AT Chainlink

Your endpoint, ready in one line.

Drop this URL into your RPC client, HTTP library or wallet config. No SDK install required.

HTTPS

https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron

WEBSOCKET

wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/tron

NATIVE gRPC

endpoints.boltrpc.io:443

Native gRPC over HTTP/2 with the official generated clients; send your API key in the x-api-key metadata header.

gRPC-WEB

https://endpoints.boltrpc.io/grpc/tron

Replace YOUR_API_KEY with your API key. Get a free key →

Pick your stack.

Copy-paste examples for the libraries you already use. Swap the API key, hit run.

import { TronWeb } from "tronweb";

const tronWeb = new TronWeb({
  fullHost: "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron",
});

const block = await tronWeb.trx.getCurrentBlock();
console.log("Block:", block.block_header.raw_data.number);

const base = "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron";

const block = await fetch(`${base}/wallet/getnowblock`, { method: "POST" })
  .then((r) => r.json());
console.log("Block:", block.block_header.raw_data.number);

import { ethers } from "ethers";

// Tron's Ethereum-compatible JSON-RPC lives under /jsonrpc
const provider = new ethers.JsonRpcProvider(
  "https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron/jsonrpc"
);

const blockNumber = await provider.getBlockNumber();
console.log("Latest block:", blockNumber);

curl -X POST https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron/wallet/getnowblock

Connect your exchange, payment backend, or dApp to Tron Mainnet with BoltRPC. Tron is the largest USDT settlement network in crypto and predictable request-unit pricing keeps your API costs flat while stablecoin volume flows through your systems around the clock.

Chain at a Glance


Protocol	Tron full-node HTTP API (TVM execution)
Block time	~3 seconds
Primary asset	USDT (TRC-20) alongside native TRX
Gas model	Bandwidth and energy, paid or staked in TRX
Smart contracts	TVM (Solidity-derived)
EVM compatible	Partially (TVM; own API and address format)
Chain ID (JSON-RPC)	728126428 (0x2b6653dc)
Block explorer	tronscan.org

What Tron is Built For

Tron’s role in crypto is unambiguous: it is where dollars move. More USDT circulates and settles on Tron than on any other network, with low fees and three-second blocks making it the default rail for exchange transfers, remittances and merchant payments across much of the world. Technically Tron runs the TVM, a Solidity-derived virtual machine, but its interface is its own: clients use the full-node HTTP API (the wallet/* routes made familiar by TronGrid) and the TronWeb SDK, with base58 addresses starting with T. The workload profile is payments infrastructure at its purest. Exchanges scan every block for TRC-20 deposits, payment processors confirm transfers continuously and all of it is sustained read volume where shared public endpoints throttle first and your users notice immediately.

Tron native gRPC

The wallet API is also served over native gRPC, the surface TronGrid sells and Tron-native tooling speaks: protocol.Wallet on the full-node tier and the finalized protocol.WalletSolidity mirror, plus gRPC-Web for browsers at https://endpoints.boltrpc.io/grpc/tron. Native gRPC is on endpoints.boltrpc.io:443 over HTTP/2 with your API key in the x-api-key metadata header. The method allowlist is the same as the HTTP wallet surface and because Tron’s gRPC is unary-only, every gRPC call bills exactly what its HTTP twin bills.

Common Use Cases on Tron

Exchange deposit and withdrawal infrastructure Scanning every block for TRC-20 deposits and broadcasting withdrawals is the canonical Tron workload: block-by-block reads, transaction lookups and scheduled broadcasts, around the clock.

USDT payment processors Invoice and remittance systems watch addresses for incoming transfers and confirm them within seconds. Chain-tip tracking and transaction lookups directly gate the customer’s payment experience.

Wallets and portfolio trackers Balance and resource lookups run on every wallet open, multiplied across TRX, USDT and other TRC-20 assets. Read latency here is perceived app speed.

Analytics and compliance Flow tracking and reporting over stablecoin volume read large ranges of blocks and transactions, a batch workload where fixed per-method pricing keeps large jobs predictable.

Built for teams that ship on Tron.

Built for USDT deposit detection

Exchanges and payment processors scan every three-second block for TRC-20 transfers. That is sustained, block-by-block read load; a dedicated endpoint keeps the scan loop ahead of the chain instead of behind it.

TronGrid-compatible routes

The endpoint serves the standard full-node HTTP API, so TronWeb and existing TronGrid-style integrations move over by changing the fullHost URL. No SDK changes, no method translation.

Reliable broadcasts

wallet/broadcasttransaction against well-connected nodes propagates withdrawals fast. When a customer is watching a pending USDT withdrawal, broadcast reliability is support load you do not get.

Predictable pricing at settlement volume

Every route has a fixed, published request-unit weight. High-volume settlement days change your request count, not your pricing model.

The stablecoin rails from one provider

BoltRPC serves Tron alongside Plasma, Celo, Ethereum and every other network on the platform behind one dashboard and one key pattern. Multi-rail payment systems talk to every chain through the same provider.

EVM-style JSON-RPC on the same key

Tron exposes an Ethereum-compatible JSON-RPC interface next to the wallet API. BoltRPC serves it at /tron/jsonrpc with chain ID 728126428, so ethers.js, viem and web3.js read Tron blocks, balances and TRC-20 contract state with the tooling you already run on EVM chains.

WebSocket block stream included

Tron's full-node API is HTTP, so BoltRPC synthesizes a newHeads stream over WebSocket: one message per block, every three seconds, gap-free, at 3 request units per message. Deposit scanners react the moment a block lands instead of polling /wallet/getnowblock.

Full JSON-RPC coverage.

Every standard Tron method you would expect. Archive-only methods are available on request for qualifying plans.

STANDARD6

POST /wallet/getnowblockPOST /wallet/getblockbynumPOST /wallet/gettransactionbyidPOST /wallet/broadcasttransactionPOST /wallet/getaccountPOST /wallet/triggerconstantcontract

Tron, explained.

Common questions about connecting to Tron over BoltRPC.

Ask a question →Read the docs

: The Tron Mainnet endpoint with BoltRPC is https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron. Replace YOUR_API_KEY with your API key from dashboard.boltrpc.io and use the standard full-node routes (for example /wallet/getnowblock) under it.
: Yes. Set fullHost to your BoltRPC endpoint when constructing TronWeb and every SDK call works unchanged. Existing TronGrid integrations migrate by swapping that one URL.
: Partially. Tron runs the TVM, a Solidity-derived virtual machine, so contracts feel familiar, but the chain has its own API (the full-node HTTP routes), its own address format (base58, starting with T) and its own resource model. Use TronWeb rather than ethers.js or MetaMask.
: Tron uses bandwidth and energy instead of a simple gas price. Accounts get free daily bandwidth. Staking TRX earns bandwidth and energy; unstaked usage burns TRX. TRC-20 transfers such as USDT consume energy.
: More USDT settles on Tron than on any other network. Low fees and three-second blocks made it the default rail for exchange transfers, remittances and merchant payments in much of the world.
: Public Tron APIs apply strict per-key and per-IP rate limits that deposit scanners hit quickly; a chain settling this much stablecoin volume generates heavy read traffic. A dedicated endpoint removes those ceilings.
: Yes, for new blocks. The Tron full-node API is HTTP, so the endpoint synthesizes a newHeads stream over WebSocket at wss://endpoints.boltrpc.io/ws/YOUR_API_KEY/tron: one message per block, every three seconds, 3 request units each. Subscribe, then fetch the block with /wallet/getblockbynum and scan it for the transfers you care about.
: Yes, for reads. Tron's EVM-compatible JSON-RPC is served at https://endpoints.boltrpc.io/rpc/YOUR_API_KEY/tron/jsonrpc with chain ID 728126428 (0x2b6653dc). ethers.js, viem and web3.js can query blocks, balances, logs and TRC-20 contracts through it. For signing and broadcasting transactions use TronWeb, which handles Tron's own address and transaction format.

Ship on Tron this week.

An API key in under 60 seconds, Tron plus 35+ other chains, and a team that answers when you write.

Start free trial View pricing