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 47 1218304 0002f2c840d4… now
GrinExplorer / Nuremburg (DE) node 5.0.4 129 1218305 00005ed304ae… now
GrinExplorer / Falkenstein (DE) node 5.0.1 96 1218305 00005ed304ae… now
GrinExplorer / Grin++ node / Helsinki (FI) 1.2.5 15 1218305 00005ed304ae… now
David Tavarez / Grin++ node / Augsburg (DE) 1.2.6 28 1218304 0002f2c840d4… now
David Tavarez / Grin++ node / Bodman-Ludwigshafen (DE) 1.2.6 18 1215555 0003dc5be0ff… 1d 22h 13m ago
David Tavarez / Grin++ node / Frankfurt am Main (DE) 1.2.6 26 1215582 00010f80f697… 1d 21h 42m ago
grinnode.live / node 1 5.1.0 57 1218304 0002f2c840d4… now
grinnode.live / node 2 5.1.0 38 1218305 00005ed304ae… now
grinnode.live / node 3 5.1.0 35 1218304 0002f2c840d4… now
grinnode.live / node 4 5.1.0 62 1218305 00005ed304ae… now
grinnode.live / node 5 5.1.0 35 1218304 0002f2c840d4… now

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