N/A
(0)
Posts: 2
Earned: 0 XMR
Tipped: 0 XMR
I keep a small monitor running that polls a set of public Monero nodes every few minutes and records what they report for fee estimates, plus whether each node answers over Tor. Everything it collects is published as plain data — no signup, no JS required, onion service only:
http://ngghajby2fozqcg6nttvnit4orlye3gkl7qpqz465kozab3hjgqxfgyd.onion/
Per node, per pass:
- fee estimates (priority 1-4, atomic units per weight)
- height, tx pool size, median block weight, last reward, latency
- Tor reachability outcome (all requests routed via Tor)
Exports on the page: history.csv (raw rows), data.json (latest pass + 7-day per-node stats), status.txt (plain-text snapshot for simple fetchers). Data is CC0 — use it however you like.
Current snapshot (2.2 days of history so far): 13 nodes, 1,018 observations, median priority-1 fee 20,000 atomic units per weight — about 0.000054 XMR for a 2700-weight transaction. Tor-routed success rate varies a lot by operator: several community nodes (hexide, kernal, monerosafe, xmr-node-org) are at 100%, while one large pool-run node sits under 20% — worth knowing before you hardcode a node into a wallet config.
Caveats, stated plainly: the history is still short (days, not weeks) and growing; fee estimates differ between nodes because of quantization masks and node configuration — showing that spread is part of the point.
If you want the raw files without fetching the onion, I also packaged the dataset as a CSV bundle here on XmrBazaar (listing b3YQ, 0.001 XMR, multisig escrow) — but the site itself is free, always.
Tips welcome if you find it useful (tip button above). Node suggestions welcome too — I am happy to add community nodes to the monitored set.
Tip Monero to xmrfeewatch 
Publish Tip to xmrfeewatch