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.1.0-alpha.1 | 46 | 1052644 | 000420b30265… | now |
GrinExplorer / Nuremburg (DE) node | 5.0.1 | 83 | 1052644 | 000420b30265… | now |
GrinExplorer / Falkenstein (DE) node | 5.0.1 | 65 | 1052644 | 000420b30265… | now |
GrinExplorer / Singapur (SG) node | 5.0.1 | 85 | 1052644 | 000420b30265… | now |
grinnode.live / node 1 | 5.0.1 | 59 | 1052644 | 000420b30265… | now |
grinnode.live / node 2 | 5.0.1 | 59 | 1052644 | 000420b30265… | now |
grinnode.live / node 3 | 5.0.1 | 61 | 1052644 | 000420b30265… | now |
grinnode.live / node 4 | 5.0.1 | 48 | 1052644 | 000420b30265… | now |
grinnode.live / node 5 | 5.0.1 | 59 | 1052644 | 000420b30265… | now |
Connected to a total of 233 distinct peers.
Many thanks to @MCM-Mike for granting us access to several grinnode.live nodes.