GrinExplorer Node Health

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 1183230 00013597eff2… now
GrinExplorer / Nuremburg (DE) node 5.0.4 143 1183230 00013597eff2… now
GrinExplorer / Falkenstein (DE) node 5.0.1 91 1183229 0003fe737ec0… now
GrinExplorer / Singapur (SG) node 5.0.4 123 1183230 00013597eff2… now
GrinExplorer / Grin++ node / Helsinki (FI) 1.2.5 15 1183230 00013597eff2… now
David Tavarez / Grin++ node / Jülich (DE) 1.2.6 15 1183230 00013597eff2… now
David Tavarez / Grin++ node / Augsburg (DE) 1.2.6 11 1183230 00013597eff2… now
David Tavarez / Grin++ node / Bodman-Ludwigshafen (DE) 1.2.6 16 1183230 00013597eff2… now
David Tavarez / Grin++ node / Frankfurt am Main (DE) 1.2.6 20 1183230 00013597eff2… now
David Tavarez / Grin++ node / Münster (DE) 1.2.6 25 1183229 0003fe737ec0… now
grinnode.live / node 1 5.0.4 55 1183230 00013597eff2… now
grinnode.live / node 2 5.0.4 32 1183229 0003fe737ec0… now
grinnode.live / node 3 5.0.4 35 1183230 00013597eff2… now
grinnode.live / node 4 5.0.4 34 1183230 00013597eff2… now
grinnode.live / node 5 5.0.4 33 1183229 0003fe737ec0… now

Connected to a total of 339 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++.