status.genoryn.org

Status

Live health of the genoryn.io mainnet node, indexer, miner and peers as seen from this server.

Checking systems…
Connecting to the genoryn.io node…
Full node (genorynd)
checking…
checking
Indexer
checking…
checking
Public mainnet seed (P2P 29710)
checking…
checking
CPU miner
checking…
checking
Live stream (SSE)
checking…
checking
Block production
checking…
checking
Chain ID
—
Height
—
Network hashrate
—
Connected now · seeds
—
Est. miners
—
estimate · network hashrate ÷ ~200 H/s per CPU
Reachable nodes
—
network crawler
Mempool
—
Node database
—

Block solve times · last 40 blocks

target 60 s

Peers of the genoryn.io node

Addresses are masked; onion peers are never shown
Connected
—
Synced
—
Still syncing
—
new nodes, 100+ blocks behind
Over Tor
—
onion peers
Highest reported
—
—
PeerDirectionLast reported heightState
Loading…

How big is the whole network? GENORYN has no central registry, so nobody can list every node. Two numbers bound it: reachable nodes (found by a crawler that walks the network through the peer protocol — only nodes with free inbound slots answer), and estimated miners (network hashrate divided by a typical light-mode CPU). The real network is at least as large as the largest of them.

This list shows the connections of this one node (at most 32 at a time — the protocol limit per node). "Last reported height" is what a peer told us when it connected or last announced a block; connected peers keep receiving every new block from us, so a slightly older number does not mean they are behind. The whole network is far larger: GENORYN has no central registry of nodes, and peers reached through Tor are counted but never listed.