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 (19)

The last scan happened 2025-12-29 00:16:30 UTC

Endpoint Block Height Tx Index Moniker Validator
140.235.158.28:26657 9,601,001 - 15,283,116 on provider-1-sentry-2 no
141.94.138.48:26677 9,949,000 - 15,283,117 on stakely ⚠️ yes
93.159.130.38:27657 10,970,001 - 15,283,117 on Bro_n_Bro ⚠️ yes
136.243.88.91:3301 11,610,001 - 15,283,117 off provider_testnet ⚠️ yes
140.235.158.31:26657 11,610,001 - 15,283,116 on provider-1-archive-1 no
148.72.141.31:26707 12,069,001 - 15,283,113 on stk-619 ⚠️ yes
140.235.158.25:26657 12,861,001 - 15,283,116 off provider-1-seed-1 no
140.235.158.26:26657 12,861,001 - 15,283,116 off provider-1-seed-2 no
176.9.30.178:14957 13,082,001 - 15,283,117 on cosmos-test ⚠️ yes
65.108.127.249:2001 13,188,001 - 15,283,116 on provider ⚠️ yes
222.106.187.14:53902 13,451,001 - 15,283,116 on Cosmostation ⚠️ yes
185.209.176.25:26657 13,813,001 - 15,283,117 on DELIGHT ⚠️ yes
144.76.79.28:29457 14,454,001 - 15,283,116 on cryptonode.tools no
64.34.93.23:26657 14,640,001 - 15,283,116 on provider no
140.235.158.29:26657 14,655,001 - 15,283,117 off provider-1-sync-1 no
140.235.158.30:26657 14,655,001 - 15,283,113 off provider-1-sync-2 no
23.88.13.45:33102 14,665,001 - 15,283,113 on CryptoSJnet no
65.21.74.120:26657 14,770,001 - 15,283,116 on node no
195.201.197.246:30657 15,278,001 - 15,283,116 on Citizen Web3 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.