RandomX rx/0Plain Stratum · no accountCommunity Infrastructure Pool
Mine Monero · XMR PUB POOL & the network
Point XMRig at our high-speed Stratum endpoints to mine on P2Pool and support the xmr.pub public
infrastructure — or launch a dedicated instance at
P2Pool Instant for 100% personal payouts.
Below is the live state of the Monero network as seen by our own full node.
Monero block height
—
from our own full node
Network hashrate
—
difficulty ÷ 120 s
Last block reward
—
network-wide
XMR PUB POOL · pool.xmr.pub:3334
—
Stratum · rx/0
P2Pool Instant · dedicated instance
Your own P2Pool node — 0% fee, no custody, no blockchain download
A dedicated P2Pool instance bound to your own Monero address, so every share pays you directly.
New here? Use the nano port above — its share difficulty is tuned for small rigs, so a
single CPU sees accepted shares within minutes instead of hours. The mini port is aimed at
larger farms.
Pool status—
Read this before pointing hashrate here. P2Pool keeps exactly one payout address per node
(--wallet), and the address a miner sends as username is ignored by the protocol.
Hashrate on these two endpoints therefore mines to the xmr.pub infrastructure wallet, which pays for
this public node and portal. We state it plainly instead of implying otherwise.
Want the rewards in your own wallet? That is a separate product and it is already live:
P2Pool Instant gives you a dedicated P2Pool instance on your own address —
0% fee, no custody, no blockchain download.
Monero network
checking…
Live from our own full node (restricted RPC)
Block height—
Difficulty—
Network hashrate—
Tx pool—
Last block reward—
Last block age—
Target block time120 s
Node status—
Network hashrate is derived as difficulty ÷ 120 s.
./xmrig -a rx/0 -o pool.xmr.pub:3334 -u my-rig -p x
-u is only a worker label — it is the name that shows up in the worker list below.
P2Pool ignores wallet addresses sent by miners; to be paid to your own address, use
P2Pool Instant instead.
Prefer encryption? Set "tls": true and keep the same endpoint — TLS is detected
automatically and terminated at the pool edge with a valid Let's Encrypt certificate for
pool.xmr.pub. Dedicated TLS ports are also available: :3335 (mini) and
:3336 (nano).
Workers on this node
Live view of every rig pointed at these endpoints. Open to miners anywhere on the internet — connect a miner and it appears here.
Workers connected
—
pointed at this node
Node hashrate
—
15 min average
Mini sidechain
—
pool.xmr.pub:3333
Nano sidechain
—
pool.xmr.pub:3334
Worker
Sidechain
Hashrate
Share difficulty
Expected interval
Connected for
Loading…
Your rig nameset -u <name> and it appears here; unnamed rigs show as anonymous
Privacyonly name · hashrate · difficulty · connected time are published — miner IP addresses are never shown, masked or otherwise
Instances paying to a miner's own wallet—
Connection history
Every TCP connection that reaches pool.xmr.pub:3333 / :3334, classified.
Most of them are internet-wide security scanners, not miners — only a connection that
actually stays and submits shares becomes a worker (see the list above).
Real miners
—
stayed connected
Handshake only
—
logged in, then left
Security scanners
—
known scan infrastructure
Port probes
—
connected, sent nothing
Recent connections
window — ·
— IPs ·
updated —
Time (UTC)
Source
Class
PTR
Bytes in
Session
Loading…
Miner IPs are masked by policy. Only connections whose reverse DNS matches known public
scanning infrastructure (Shadowserver, Shodan, Modat, …) are shown in full.
We deliberately do not republish their feed here: the data endpoint returns 404 to non-browser
requests and other providers require an API key. Rather than show numbers that could be stale, this page
shows only what we can verify ourselves — XMR PUB POOL's reachability and our own node's view of the network.
If you want a live network-wide pool chart on this page, provide a stats API key (e.g. Minerstat) and we
will wire it in.