PublicNode vs TronGrid

TronGrid leads on the only live benchmark. TronGrid wins on Fastest free TRON RPC, live no-key JSON-RPC endpoint latency (13 ms vs 153 ms).

Read methodology Last measured Window: rolling 24h1 shared benchmark
PublicNode logo
PublicNode

Public no-key RPC service operated by Allnodes covering 70+ chains. JSON-RPC and WebSocket endpoints with archive support on most networks.

TronGrid logo
TronGrid

TRON Foundation's official public API gateway (api.trongrid.io). Serves both the native TRON REST API (wallet/getnowblock, wallet/triggersmartcontract) and an EVM-compatible JSON-RPC endpoint (/jsonrpc). Keyless with a free API-key tier for higher quotas. The reference endpoint every TronWeb/tronbox integrator points at first.

Side by side measurements

Frequently asked questions

PublicNode vs TronGrid: which one is better?

PublicNode and TronGrid are compared on 1 shared OpenChainBench benchmarks. TronGrid leads on Fastest free TRON RPC, live no-key JSON-RPC endpoint latency. See the live table on this page for every metric.

Which is faster, PublicNode or TronGrid?

On the Fastest free TRON RPC, live no-key JSON-RPC endpoint latency benchmark, TronGrid leads at 13 ms versus PublicNode at 153 ms. Live measurement is updated continuously by the OpenChainBench harness.

How is the PublicNode vs TronGrid comparison measured?

Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.

How this pair was selected

Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.

Live data refreshes via ISR within 60 seconds of a new run. Sources are the same Prometheus queries surfaced on the parent benchmark pages.