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 (16)
The last scan happened 2025-06-22 00:23:08 UTC
| Endpoint | Block Height | Tx Index | Moniker | Validator |
|---|---|---|---|---|
| 140.235.158.26:26657 | 4,273,001 - 12,423,035 | off | provider-1-seed-2 | no |
| 140.235.158.25:26657 | 4,273,001 - 12,423,034 | off | provider-1-seed-1 | no |
| 140.235.158.29:26657 | 4,273,001 - 12,423,033 | off | provider-1-sync-1 | no |
| 176.9.30.178:14957 | 7,804,016 - 12,423,034 | on | cosmos-test | ⚠️ yes |
| 140.235.158.27:26657 | 9,601,001 - 12,423,031 | on | provider-1-sentry-1 | no |
| 141.94.138.48:26677 | 9,949,000 - 12,423,034 | on | stakely | ⚠️ yes |
| 93.159.130.38:27657 | 10,970,001 - 12,423,034 | on | Bro_n_Bro | ⚠️ yes |
| 65.21.24.47:26657 | 11,423,035 - 12,423,035 | on | node | no |
| 3.127.145.33:26657 | 11,608,501 - 12,423,034 | off | AAA | ⚠️ yes |
| 222.106.187.14:53902 | 11,610,001 - 12,423,035 | on | Cosmostation | ⚠️ yes |
| 136.243.88.91:3301 | 11,610,001 - 12,423,034 | off | provider_testnet | ⚠️ yes |
| 140.235.158.31:26657 | 11,610,001 - 12,423,031 | on | provider-1-archive-1 | no |
| 168.119.89.91:33102 | 12,037,000 - 12,423,034 | on | CryptoSJnet | no |
| 148.72.141.31:26707 | 12,069,001 - 12,423,034 | off | stk-619 | no |
| 143.110.211.69:26657 | 11,952,001 - 12,039,613 | on | 143.110.211.69 | no |
| 195.201.197.246:30657 | 12,417,001 - 12,423,034 | on | Citizen Web3 | no |
⚠️ 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.