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-04-22 00:04:08 UTC

Endpoint Block Height Tx Index Moniker Validator
37.27.136.45:26657 1 - 13,443,730 on archive-node-hetzner1 no
149.202.66.111:36657 1 - 13,443,729 on archive-node-full-1 no
23.88.13.39:26657 1 - 13,443,729 on archive-node-hetzner-2 no
65.108.70.119:33657 7,894,001 - 13,443,730 on AlxVoy no
164.68.125.243:26657 9,101,801 - 13,443,730 on Smt Network ⚠️ yes
5.135.141.191:26657 10,276,001 - 13,443,729 on c4e-sentry1-mainnet no
139.144.96.120:26657 10,379,001 - 13,443,730 on grenton-sass-mainnet ⚠️ yes
185.245.182.192:46657 12,307,101 - 13,443,729 on Meerlabs ⚠️ yes
65.109.30.185:26657 12,739,001 - 13,443,729 on c4e-sentry2-mainnet no
65.109.78.246:26457 12,991,501 - 13,443,730 on c4e-rpc no
148.251.9.235:26657 13,101,670 - 13,443,730 on c4e-relayer2 no
65.109.125.189:26657 13,101,670 - 13,443,730 on relayer1 no
163.172.18.144:26657 13,129,001 - 13,443,729 on c4e-sentry3-mainnet no
77.55.216.80:26657 13,189,501 - 13,443,729 on c4e-sentry4-mainnet no
163.172.18.162:26657 13,235,001 - 13,443,730 on c4e-dao3-mainnet ⚠️ yes
172.105.229.177:26657 13,376,001 - 13,443,730 on ovoo-sass-mainnet ⚠️ yes
65.108.121.227:16657 13,429,001 - 13,443,729 on landeros-rpc no
168.119.226.107:26957 13,437,001 - 13,443,727 on c4e_rpc no
65.21.136.219:17097 13,441,301 - 13,443,729 on STAVR-Service 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.