monerospace.org

Browser-based Monero mempool + block explorer. Operator-published positioning (homepage `<meta>`): *"Explore Monero blocks, mempool activity, RingCT transaction metadata, fee tiers, and live network state with monerospace.org."* Same product shape as `mempool.space` (Bitcoin's canonical mempool UI) but for Monero — a real-time view of the chain's pending-transaction pool, recent blocks, fee distribution, and current network state. Listed at Grade B on first pass: useful read-only tool with no operator-side trust requirements (you're just looking at on-chain data), but the operator surface is sparse (JS-only SPA, no published team / repo / license / Tor onion / contact at submission time) so the upgrade-to-A path is conditioned on operator transparency improvements.

What it is. Single-page React/Vite app at `monerospace.org` serving a live view of the Monero chain. Reads from a Monero daemon (operator-run, presumably) and renders the mempool, recent blocks, fee tiers, RingCT transaction metadata. No account, no API key, no payment, no registration. The data is public — Monero is a transparent chain at the transaction-graph level (just opaque on amounts + senders) — so a third-party explorer can render it without trust from the user.

Background. Newer project (homepage live as of 2026-05). Distinct from the older `monero.space` (with no `.org`) — that one is the Monero events / MoneroKon org on GitHub (`github.com/MoneroSpace`), a separate entity hosting community work like Defcon Cryptocurrency Village. `monerospace.org` (the explorer) appears to be unaffiliated with that events org; we have not yet identified the operator. If the maintainer publishes themselves we will update this entry.

What you trust.

• Read-only. You never deposit, sign, or transmit anything — the worst case is the operator showing you wrong data (which would be obvious against any second source like `xmrchain.net` or `localmonero.co/blocks`).
• Public chain data. Monero's chain is queryable by anyone; the explorer just renders what a `monerod` node exposes via RPC. No operator-side privileged information.
• No account, no signup, no payment. Open the page, browse. No tracking gate.
• Browser-only. Connection terminates at the explorer's backend; no Tor mirror published at submission time, so on clearnet the operator (and their CDN, if any) sees your IP + which blocks/transactions you queried.
• No published team / license / repo. Operator anonymity is normal in this tier — flagged as a transparency caveat, not a blocker.

Operational specs.

• Site. React/Vite SPA — JS required to render. Every route serves the same ~3 KB HTML shell; content hydrates client-side.
• Data surface. Mempool, recent blocks, RingCT metadata, fee tiers, network state. Documented in the homepage meta description.
• API. No `/api` endpoint surfaced (the `/api*` paths return 404 against the shell). If the operator opens one, we'll re-evaluate.
• Tor. No published `.onion` mirror at submission time. Use the clearnet site via Tor Browser for now.
• Pricing. Free. No commercial tier disclosed.
• Contact. No published `/contact` or operator email surfaced. Updates depend on operator outreach.

Operator philosophy. Unstated. The product (a free, no-account Monero mempool view) is in the same lineage as `xmrchain.net`, `localmonero.co/blocks`, the Monero-project-maintained `moneroblocks.info`, and `mempool.space` — community-run explorer infrastructure that complements running your own node.

Grade rationale. Grade B because: (1) no operator-published team / license / repo / contact disclosure; (2) no Tor onion advertised — clearnet only; (3) JS-only SPA with no SSR fallback or no-JS path; (4) no third-party review or cross-listing verified at submission time (kycnot.me + monerica + privacyguides not yet checked). The product itself is a low-trust-requirement read-only tool, so the Grade B floor is justified by the operator-transparency gap, not by product-side risk. Upgrade-to-A path: operator publishes team / license / repo + ships a Tor onion + maintains a clean uptime record over 90+ days.

Useful when:

• You want to glance at the current Monero mempool — pending transactions, fee distribution, recent blocks.
• You're tracking a specific transaction you just submitted and want to see when it lands in a block.
• You're a researcher studying mempool patterns, fee tiers, or RingCT metadata.
• You're cross-checking another explorer's data against a second source (the right way to use any single block explorer).

Caveats:

• JS-only. No-JS users see an empty 3 KB shell. Mempool / block / tx queries require a browser with JS enabled.
• No Tor onion at submission time. Clearnet only — the operator sees your IP + your queries unless you route through Tor Browser.
• No operator-published team / license / repo / contact. Anonymous-operator tier; trust accumulates through uptime + cross-source agreement, not formal disclosure.
• Disambiguation: `monerospace.org` ≠ `monero.space` (no `.org`). The latter is the older Monero events / MoneroKon org. Different team, different product. We list each separately if both end up earning a slot.
• No second source verified yet. Cross-check what the explorer shows against `xmrchain.net` or your own `monerod` before relying on it for anything material.
• First-pass listing; no curator end-to-end check on file yet. Grade B default per the playbook for new submissions; full re-grade conditional on the upgrade items above + at least one cross-source verification pass.