What is a TON RPC node?

A TON RPC node is a server that exposes TON's API, allowing applications to query blockchain data, submit transactions, and interact with smart contracts on TON mainnet and testnet. Developers use TON RPC nodes to power Telegram Mini Apps, wallets, payment processors, and DeFi protocols without running their own node infrastructure.

How does TON RPC support Telegram Mini Apps?

TON RPC endpoints let Telegram Mini Apps (TMAs) read on-chain data, submit user transactions, and verify payments in real time. Because TON is the native blockchain layer for Telegram ecosystem, reliable RPC access is essential for any project targeting Telegram's user base, particularly under viral traffic conditions.

What is GetBlock's TON RPC service?

GetBlock provides managed TON RPC nodes with high-availability endpoints for TON mainnet (and testnet on dedicated nodes). Developers get the JSON-RPC (TON Center v2-style) API, HTTP API v4 and Indexer API v3 without managing node binaries, shard archives, or peer discovery.

Which wallets support TON RPC connections?

TON endpoints are compatible with all major TON-compatible wallets, including the built-in Wallet in Telegram.

What data can TON RPC nodes access?

TON RPC nodes return account balances, address states, transaction histories, smart contract states, Jetton (token) data, NFT records, masterchain and shardchain information, and block data.

How do I connect to TON RPC?

Connect to TON RPC using GetBlock's HTTPS endpoint, along with a TON-compatible SDK in your preferred language. No private keys or sensitive credentials are required to read public chain data – only your API key from GetBlock.

What are common TON RPC methods?

Frequently used TON RPC methods include getMasterchainInfo, getAddressInformation, getAddressBalance, getTransactions, getBlockTransactions, runGetMethod, sendBoc, and detectAddress. These cover wallet integration, payment flows, smart contract reads, and indexing.

Does TON RPC support real-time data streaming?

GetBlock's TON endpoints are HTTP-based, so applications usually poll getTransactions or query the Indexer API v3 for payment monitoring and trading bots. For lower-level real-time access, TON's native ADNL protocol lets clients talk to lite-servers directly.

What is the TON Chain ID?

TON does not have a "chain ID" in the way EVM chains do. It uses a network ID of -239 for mainnet and -3 for testnet. This is an internal protocol-level value – developers don't need to set it manually. Connection to mainnet or testnet happens via the endpoint URL or the global config file. TON also uses workchain IDs (-1 for masterchain, 0 for basechain) in address formatting.

Does TON have a block explorer?

Yes. Several TON block explorers are available, providing detailed views of transactions, addresses, Jetton transfers, NFT activity, and smart contract states on TON.

GetBlock

RPC Service

TON

TON RPC for Telegram apps

Build Mini Apps, payments and wallets for Telegram users on TON with instant RPC access.

Node options

Networks

APIs

Add-ons

Advanced Analytics
Private Grafana with latency percentiles and error rates per method, key and region.
- dedicated
Automatic RPC Failover
If your node degrades, traffic shifts to shared RPC and back, on the same endpoint URL.
- dedicated
Custom Endpoint URL
Serve the node from your own domain and move the access token from the URL to a header.
- dedicated
Dedicated Ingress Proxy
A proxy fleet that serves only you: TLS, auth and rate limits isolated from other users.
- dedicated
IP Allowlist
Only approved IPs and CIDR ranges get in, so a leaked token alone won’t reach your node.
- dedicated
Nonstandard Client Support
Pinned client versions, forks and custom flags, run and maintained by our engineers.
- dedicated
Unified Multichain Endpoint
One URL and credential for all your dedicated nodes, with the chain set by subdomain.
- dedicated
Zero-Hop Node Access
Requests hit your node directly, past the gateway and load balancer, for lower latency.
- dedicated

Free

$0 /month

Best for: prototypes, Mini App experiments, side projects, and first integrations.

Shared TON mainnet endpoint
50K Compute Units a day, no card required
JSON-RPC, HTTP API v4 and Indexer API v3 access
Keys, usage and limits in one dashboard
Upgrade to a paid Shared plan whenever traffic grows

Shared Node

from $49 /month

Best for: wallets, Mini Apps, payment services and mid-traffic workloads.

High-performance TON RPC endpoint
Scalable RPS tiers (250 – 800 RPS)
JSON-RPC, HTTP API v4 and Indexer API v3 on one API key
Monitoring & standard SLA (99.99% uptime guaranteed)

Limitless Node

from $250 /month

Best for: bots, indexers and Mini App backends that need steady throughput at a flat price.

Isolated TON full node with guaranteed RPS
Four fixed throughput tiers, from $250 to $1,200 a month
Unlimited requests inside the tier — no Compute Units
No concurrent connection limits
Frankfurt region

Dedicated Node

Recommended

from $1,700 /month

Best for: exchanges, custodians, payment processors and enterprise environments.

Dedicated TON node with unlimited RPS
Full node from $1,700, archive from $2,500
Mainnet and testnet in Frankfurt, Singapore or New York
JSON-RPC, HTTP API v4 and Indexer API v3
99.99% uptime SLA
Add-ons: analytics, RPC failover, IP allowlist, zero-hop access
On-premise deployment available

AT A GLANCE

TON network specifications

Architecture & Consensus Model	Sharded Layer 1, Proof-of-Stake (Byzantine Fault Tolerant)
Launch Date	November 15, 2019 (genesis)
Average Block Time	~400ms
Throughput (TPS)	Dynamic sharding; 104,715 TPS in a public 2023 performance test
Gas Token	Toncoin (TON)
Smart Contract Support	Yes (TON Virtual Machine)
Programming Languages	Tolk, FunC, Tact
Notable Use Cases	Telegram Mini Apps, payments, DeFi, NFTs, gaming, AI agents
Chain ID	Not applicable; network ID -239 (mainnet), -3 (testnet)
Data Availability Layer	Native on-chain
State Validation	Native validators
Sequencer / Block Proposer	Validators, in rotation within each shard
Network Type	Public
Transaction Privacy	None
Transaction Ordering	Validator-determined, by logical time

Low-latency API endpoints

Response times as low as 14 ms with globally distributed infrastructure for consistent performance.

High throughput capacity

Multiple connection protocols

Mainnet and testnet access

99.99%+ uptime

Low-latency API endpoints

Response times as low as 14 ms with globally distributed infrastructure for consistent performance.

200k+developers registered on the platform
100,000+hours of Web3 DevOps engineering invested in the GetBlock infrastructure
6 yearsof infrastructure development expertise

Non-Custodial Wallets
124MActive users
Trust Wallet consolidated 12 networks onto managed infrastructure, with an estimated 4,500 engineering hours saved.
Read the case study
Crypto Exchanges
40MUsers
MEXC held 99.99% uptime through peak 2024 and 2025 trading load, with an estimated 3,000 engineering hours saved.
Read the case study
Hardware Wallets
6MWallets sold
Tangem has held three years of 99.99% uptime and doubled its supported network count on GetBlock infrastructure.
Read the case study
Payment Processors
7M+Payments processed
CoinGate gained a DORA and GDPR framework built from scratch, with an estimated 1,400 hours of engineering work saved.
Read the case study
DeFi Protocols
$400B+Cumulative volume on Aerodrome
Revert moved from trial to production analytics on Base, on the first production overlay-enabled Base node we know of.
Read the case study
Web3 Security
$500B+In digital assets protected
Blockaid extended screening to networks with no commercial RPC support, with an estimated 1,500 hours of work saved.
Read the case study

ENTERPRISE

Business-tuned TON infrastructure

Redundant, secure, and SOC 2 Type II attested. Engineered for enterprise-grade uptime and trust

Dedicated Nodes & Clusters
Global node deployment
Tailored load-balancing
Guaranteed throughput
99.99%+ uptime SLA
24x7 dedicated support

SOC 2 Type II
DORA and GDPR
ISO 27001
ISO 27017

Developer DocsQuickstart guides, API references, code examples, and environment setup instructions to help you build, test, and deploy on TON blockchain.docs.getblock.io

FAQ

Everything you need to know about TON RPC nodes, network access, and choosing the right setup for your dApp.

A TON RPC node is a server that exposes TON's API, allowing applications to query blockchain data, submit transactions, and interact with smart contracts on TON mainnet and testnet. Developers use TON RPC nodes to power Telegram Mini Apps, wallets, payment processors, and DeFi protocols without running their own node infrastructure.
TON RPC endpoints let Telegram Mini Apps (TMAs) read on-chain data, submit user transactions, and verify payments in real time. Because TON is the native blockchain layer for Telegram ecosystem, reliable RPC access is essential for any project targeting Telegram's user base, particularly under viral traffic conditions.
GetBlock provides managed TON RPC nodes with high-availability endpoints for TON mainnet (and testnet on dedicated nodes). Developers get the JSON-RPC (TON Center v2-style) API, HTTP API v4 and Indexer API v3 without managing node binaries, shard archives, or peer discovery.
TON endpoints are compatible with all major TON-compatible wallets, including the built-in Wallet in Telegram.
TON RPC nodes return account balances, address states, transaction histories, smart contract states, Jetton (token) data, NFT records, masterchain and shardchain information, and block data.
Connect to TON RPC using GetBlock's HTTPS endpoint, along with a TON-compatible SDK in your preferred language. No private keys or sensitive credentials are required to read public chain data – only your API key from GetBlock.
Frequently used TON RPC methods include getMasterchainInfo, getAddressInformation, getAddressBalance, getTransactions, getBlockTransactions, runGetMethod, sendBoc, and detectAddress. These cover wallet integration, payment flows, smart contract reads, and indexing.
GetBlock's TON endpoints are HTTP-based, so applications usually poll getTransactions or query the Indexer API v3 for payment monitoring and trading bots. For lower-level real-time access, TON's native ADNL protocol lets clients talk to lite-servers directly.
TON does not have a "chain ID" in the way EVM chains do. It uses a network ID of -239 for mainnet and -3 for testnet. This is an internal protocol-level value – developers don't need to set it manually. Connection to mainnet or testnet happens via the endpoint URL or the global config file. TON also uses workchain IDs (-1 for masterchain, 0 for basechain) in address formatting.
Yes. Several TON block explorers are available, providing detailed views of transactions, addresses, Jetton transfers, NFT activity, and smart contract states on TON.

The Open Network (TON) is a high-performance Layer 1 blockchain powering everything from peer-to-peer transfers to high-throughput dApp, and Telegram Mini Apps. TON uses a sharded workchain architecture, Proof-of-Stake consensus, and the TON Virtual Machine (TVM) to deliver sub-second finality, achieved through the Catchain 2.0 consensus upgrade. The network's masterchain coordinates multiple shardchains that split and merge with load (dynamic sharding).

What sets TON apart is its native connection to Telegram. It gives developers access to one of the largest consumer audiences in crypto through Mini Apps (TMAs), in-chat payments, and bot ecosystems. TON benefits payment processors, wallet developers, DeFi protocols, gaming studios, and AI agent teams who need fast, low-cost, mobile-first blockchain infrastructure.

Ready to get started?

Launch your RPC endpoint in less than 5 clicks with reliable, production-ready access for devs who want to move fast. Like, really fast.

High-volume or custom setup?

Need dedicated throughput, custom infrastructure, or engineering services? Let our team design and deliver the solutions your business demands.

Explore our services

TON RPC for Telegram apps

Add-ons

TON Infrastructure Pricing

Free

Shared Node

Limitless Node

Dedicated Node

TON network specifications

Why build on TON with GetBlock

Low-latency API endpoints

High throughput capacity

Multiple connection protocols

Mainnet and testnet access

99.99%+ uptime

Trusted by leading Web3 teams

Business-tuned TON infrastructure

Start building on TON

FAQ

TON performance notes

Get building on TON.

Ready to get started?

High-volume or custom setup?