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

The last scan happened 2024-02-18 00:38:54 UTC

Endpoint Block Height Tx Index Moniker Validator
190.2.146.152:28657 1 - 859,408 on Kalia Network ⚠️ yes
65.109.39.223:26647 1 - 859,408 off Loona.Systems ⚠️ yes
65.108.79.246:26674 1 - 859,408 on Stakely.io ⚠️ yes
65.108.65.94:26657 1 - 859,408 on testval02 ⚠️ yes
65.108.2.27:26657 1 - 859,408 on testval03 ⚠️ yes
162.55.103.44:26647 1 - 859,407 off CryptoCats.Pro ⚠️ yes
46.4.121.72:11157 70,101 - 859,408 off nkbblocks ⚠️ yes
149.50.96.24:36657 133,501 - 859,407 on ams no
49.12.84.248:20657 146,001 - 859,408 on [NODERS]TEAM ⚠️ yes
57.128.20.238:33657 149,101 - 859,407 on Staking_Rewards ⚠️ yes
89.38.98.200:21027 220,501 - 859,408 off VivaLaFrance ⚠️ yes
65.108.226.26:30657 241,501 - 859,408 on [NODERS]TEAM_SERVICE no
65.109.93.152:37657 315,173 - 859,408 on AlxVoy ⚠️ yes
95.216.102.121:61157 748,801 - 749,821 on DTEAM 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.