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

The last scan happened 2025-07-31 00:03:38 UTC

Endpoint Block Height Tx Index Moniker Validator
23.88.13.39:26657 1 - 14,888,024 on archive-node-hetzner-2 no
5.135.141.191:26657 10,276,001 - 14,888,023 on c4e-sentry1-mainnet no
185.245.182.192:46657 12,307,101 - 14,888,023 on Meerlabs ⚠️ yes
172.105.229.177:26657 13,376,001 - 14,888,024 on ovoo-sass-mainnet ⚠️ yes
65.109.30.185:26657 14,462,001 - 14,888,022 on c4e-sentry2-mainnet no
139.144.96.120:26657 14,478,001 - 14,888,024 on grenton-sass-mainnet ⚠️ yes
148.251.9.235:26657 14,545,962 - 14,888,022 on c4e-relayer2 no
77.55.216.80:26657 14,691,701 - 14,888,018 on c4e-sentry4-mainnet no
163.172.18.144:26657 14,751,001 - 14,888,023 on c4e-sentry3-mainnet no
168.119.226.107:26957 14,788,023 - 14,888,023 on c4e_rpc no
65.108.121.227:16657 14,874,001 - 14,888,022 on landeros-rpc 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.