Blockchains
One catalogue of networks.
The pulse of each one in plain sight.
The full list with an honest status: what runs right now and what we bring up on request. Every chain shows its block time, height, latency and the address it answers on.
- 4
- Networks live
- 38
- In the catalogue
- 16 ms
- p50 latency
- 9
- Regions
Block sweep
One minute of the network. Every tick is a block.
Solanaevery 0.4 s302,847,119
Tronevery 3 s87,026,418
Ethereumevery 12 s26,171,733
Bitcoinevery 10 min970,980not a single block in a minute
Catalogue
Networks and their status
Live networks come first: block height ticking, latency measured, endpoint ready to copy. The rest we bring up for a specific project.
Showing 38 of 38 networks
- EthereumMainnetBlocksevery 12 s
Height26,171,733
Latency18 ms
liverpc.settla.net/eth/mainnet - SolanaMainnetBlocksevery 0.4 s
Height302,847,119
Latency16 ms
liverpc.settla.net/sol/mainnet - BitcoinMainnetBlocksevery 10 min
Height970,980
Latency31 ms
liverpc.settla.net/btc/mainnet - TronMainnetBlocksevery 3 s
Height87,026,418
Latency27 ms
liverpc.settla.net/trx/mainnet 
BaseMainnetBlocksevery 2 sHeight—
Latency—
On request
Arbitrum OneMainnetBlocksevery 0.25 sHeight—
Latency—
On request
OptimismMainnetBlocksevery 2 sHeight—
Latency—
On request
Polygon PoSMainnetBlocksevery 2 sHeight—
Latency—
On request
BNB ChainMainnetBlocksevery 3 sHeight—
Latency—
On request
Avalanche CMainnetBlocksevery 2 sHeight—
Latency—
On request
LitecoinMainnetBlocksevery 3 minHeight—
Latency—
On request
DogecoinMainnetBlocksevery 1 minHeight—
Latency—
On request
zkSync EraMainnetBlocksevery 1 sHeight—
Latency—
On request
LineaMainnetBlocksevery 2 sHeight—
Latency—
On request
ScrollMainnetBlocksevery 3 sHeight—
Latency—
On request
BlastMainnetBlocksevery 2 sHeight—
Latency—
On request
GnosisMainnetBlocksevery 5 sHeight—
Latency—
On request
CeloMainnetBlocksevery 5 sHeight—
Latency—
On request
SuiMainnetBlocksevery 0.4 sHeight—
Latency—
On request
AptosMainnetBlocksevery 0.25 sHeight—
Latency—
On request
TONMainnetBlocksevery 5 sHeight—
Latency—
On request
NEARMainnetBlocksevery 1 sHeight—
Latency—
On request
Cosmos HubMainnetBlocksevery 6 sHeight—
Latency—
On request
InjectiveMainnetBlocksevery 0.7 sHeight—
Latency—
On request
SeiMainnetBlocksevery 0.4 sHeight—
Latency—
On request
CronosMainnetBlocksevery 6 sHeight—
Latency—
On request
RoninMainnetBlocksevery 3 sHeight—
Latency—
On request
SonicMainnetBlocksevery 1 sHeight—
Latency—
On request- SepoliaTestnetBlocksevery 12 s
Height—
Latency—
On request - HoleskyTestnetBlocksevery 12 s
Height—
Latency—
On request - Base SepoliaTestnetBlocksevery 2 s
Height—
Latency—
On request - Arbitrum SepoliaTestnetBlocksevery 0.25 s
Height—
Latency—
On request - Optimism SepoliaTestnetBlocksevery 2 s
Height—
Latency—
On request - Polygon AmoyTestnetBlocksevery 2 s
Height—
Latency—
On request - Solana DevnetTestnetBlocksevery 0.4 s
Height—
Latency—
On request - Bitcoin TestnetTestnetBlocksevery 10 min
Height—
Latency—
On request - Tron NileTestnetBlocksevery 3 s
Height—
Latency—
On request - Sui TestnetTestnetBlocksevery 0.4 s
Height—
Latency—
On request
What's included
The same in every network
Switching chains changes one segment of the address. The key, the limits, the regions and the response format stay put.
Native JSON-RPC
The chain's own methods, word for word from its docs. Nothing to proxy or rename.
WebSocket and subscriptions
New blocks and events arrive as a stream instead of a poll every second.
Archive data
State from block zero on the same endpoints, with no separate plan for history.
One key for every chain
Adding a network means changing a segment of the address, not opening a second project with a second key.
Questions
Networks in short
Tell us which chain you need and the load you expect. Chains marked “on request” are brought up for a specific project; anything outside the catalogue we discuss separately.
Live means the network runs in production: it has an address and limits, and your key starts answering right away. On request means nodes are provisioned for the project, with timing and terms agreed up front.
Each has its own address, but the key and the limits are shared with the mainnet. Only the network segment of the address changes.
Yes. Historical state queries go to the same address and count as ordinary calls — there is no separate archive plan.
Yes, the key belongs to the project rather than to a chain. Adding a network means changing a segment of the endpoint address.
Infrastructure shouldn't be the thing slowing you down.
Free to start. No credit card required.