RPC nodes allow you to obtain information about what is happening on chain, by using HTTP requests. We scan the network and produce a list of nodes that publish their RPC endpoints. These nodes are not controlled by us, and we do not verify the correctness of the data they provide. Although we suggest you to use our managed nodes.

The block heights reported are obtained on a daily schedule. This data is provided as a snapshot of the time when data was collected.

Public RPC endpoints (21)

The last scan happened 2025-03-31 00:05:57 UTC

Endpoint Block Height Tx Index Moniker Validator
5.9.74.183:26657 5,200,791 - 25,067,373 on zipdia-v2 no
5.9.86.153:26657 5,200,791 - 25,067,368 on zipdia-v6 no
65.108.30.59:26657 23,501,000 - 25,067,374 on hello-aries no
135.181.73.170:22157 24,067,369 - 25,067,369 on Pro-Nodes_rpc no
158.247.236.153:26657 24,281,000 - 25,067,372 on bananas no
141.164.55.117:26657 24,281,000 - 25,067,370 on bananas no
64.176.46.105:26657 24,281,000 - 25,067,370 on carrotjp no
88.198.45.137:26657 24,365,999 - 25,067,374 on colossus-node5 ⚠️ yes
104.237.53.202:14957 24,365,999 - 25,067,370 on cosmos-node no
65.108.44.124:36011 24,365,999 - 25,067,369 on gaiad no
67.218.8.88:26657 24,365,999 - 25,067,369 on CryptoDungeon ⚠️ yes
103.241.50.31:29657 24,385,998 - 25,067,370 on def no
103.241.50.27:29657 24,385,998 - 25,067,370 on default no
54.177.181.170:26657 24,392,001 - 25,067,375 on aws-nc-atom1 no
52.78.35.79:26657 24,392,001 - 25,067,370 on tibrok no
88.198.59.234:26657 24,586,001 - 25,067,372 off papadritta no
65.109.83.213:36657 24,596,000 - 25,067,373 on Wetez no
157.90.33.62:24657 24,659,001 - 25,067,367 on LiveRaveN no
178.128.61.252:46657 21,014,121 - 21,130,610 on oraichain no
176.9.30.178:15057 25,060,011 - 25,067,369 on cosmos-main no
138.201.82.234:29657 25,065,000 - 25,067,365 off hello-aries no

raw scan results

⚠️ Validators or public sentries which hold voting power above 0 are marked with warning symbol. Exposed to the public network, endpoints can be used as attack vector to harm the chain. Node operators should be aware of this and have a firewall rules in place to limit the attack surface of their validator infrastructure.