Peer-to-peer
Network
The peers our NEB node is connected to, as its getpeerinfo reports them. NEB nodes talk on port 3440.
8 connected · 4 inbound · 4 outbound
Connected peers
8
4 inbound · 4 outbound
Peers at our tip
3 / 8
announced a height within 2 blocks of ours
Our tip
3,355
height of our node
Best announced height
3,355
no peer is ahead of us
Peers
Outbound first, longest connected first
8 peers
- 185.42.223.63:3440outboundneb-node/1.0.1#3,355at our tip5h 27m
- 185.195.106.72:3440outboundneb-node/1.0.1#3,250105 below our tip5h 27m
- 103.141.183.126:3440outboundneb-node/1.0.1#3,354at our tip5h 26m
- 169.58.122.42:3440outboundneb-node/1.0.1#3,32530 below our tip5h 25m
- 169.58.122.42:53794inboundneb-node/1.0.1#3,33124 below our tip5h 25m
- 116.172.94.166:44096inboundneb-node/1.0.2#4362,919 below our tip4h 31m
- 82.67.60.70:38376inboundneb-node/1.0.2#3,25699 below our tip1h 40m
- 46.150.93.11:17053inboundneb-node/1.0.2#3,353at our tip2m
Top versions
| Version | # |
|---|---|
| protocol 3 | 8 |
Top user agents
| User agent | # |
|---|---|
| neb-node/1.0.1 | 5 |
| neb-node/1.0.2 | 3 |
Peer locations
Peer locations are not shown: the node only knows its direct peers (it has no getnodeaddresses), and placing their IP addresses on a map would mean sending them to a third-party geolocation service or shipping a GeoIP database, which this server does not.
Versions, user agents and heights come from our directly connected peers. A peer’s height is the best height it has announced to us; a peer that does not relay blocks to us keeps its handshake height, so “below our tip” does not prove it is behind. “At our tip” means within 2 blocks.