The following tables shows the nodes that are powering GrinExplorer. Why so many? So that we have the broadest network overview possible and a higher chance to detect orphaned blocks and chain forks early.
| Node | Version | # Peers | Block Height | Block Hash | Last Seen |
|---|---|---|---|---|---|
| GrinExplorer / Helsinki (FI) node | 5.0.4 | 49 | 1404684 | 0001e0096dbf… | now |
| GrinExplorer / Nuremburg (DE) node | 5.0.4 | 99 | 1404684 | 0001e0096dbf… | now |
| GrinExplorer / Falkenstein (DE) node | 5.0.1 | 70 | 1404684 | 0001e0096dbf… | now |
| GrinExplorer / Grin++ node / Helsinki (FI) | 1.2.5 | 15 | 1404684 | 0001e0096dbf… | now |
| grinnode.live / node 1 | 5.1.1 | 45 | 1404684 | 0001e0096dbf… | now |
| grinnode.live / node 2 | 5.1.1 | 37 | 1404684 | 0001e0096dbf… | now |
| grinnode.live / node 3 | 5.1.1 | 34 | 1404684 | 0001e0096dbf… | now |
| grinnode.live / node 4 | 5.1.0 | 60 | 1404684 | 0001e0096dbf… | now |
| grinnode.live / node 5 | 5.1.1 | 31 | 1404684 | 0001e0096dbf… | now |
Connected to a total of 221 distinct peers.
Many thanks to @MCM-Mike for granting us access to several grinnode.live nodes and to @dtavarez for granting us access to several nodes running Grin++.