MoneroSpace

Live Monero mempool explorer — pending transactions, fee-rate bands (20k–4M ɱ/B), pool attribution (SupportXMR, HashVault, P2Pool), block heights matching mainnet. Open source at [`n0/monerospace-org`](https://github.com/n0/monerospace-org) — a port of `mempool.space` to Monero, repo created 2026-05-05, actively updated.

Live Monero mempool explorer with real-time fee estimation — shows pending transactions, fee-rate bands (20k–4M ɱ/B), and pool attribution (SupportXMR, HashVault, P2Pool). Listed at Grade B because the tool is demonstrably functional with live chain data, but 38/39 paths returned identical SPA shell content and no operator-published policy text is readable publicly.

What it is. Monero mempool explorer — a read-only public utility showing pending transactions and fee estimates on the Monero network. Listed at Grade B because the homepage renders live, plausible mempool data (operator-published), establishing functionality, but the SPA hash-route privacy/about/terms pages rendered identical shell content and zero peer-directory matches exist.

What you trust. Mempool data accuracy: The homepage shell renders live Monero chain data including block heights (3686039+, matching mainnet), fee-rate bands (20k–4M ɱ/B), pool attribution labels (SupportXMR, HashVault, P2Pool), and transaction counts per block (operator-published). The data is self-authenticating: any Monero node operator can verify the figures independently. This is the strongest trust signal for a mempool explorer — the output is checkable against the blockchain. Fee estimation: Transaction fee estimation is visible in the shell with four priority bands (No Priority / Low / Medium / High) at specific ɱ/B rates (operator-published). Accuracy of the estimation model depends on the explorer's algorithm; Privacy policy: Route exists at `#/privacy` but rendered identical mempool-data shell. For a mempool explorer, the key question is whether the operator logs IP addresses, query patterns, or block data requests. This is unreadable publicly. Terms of service: Routes exist at `#/terms` and `#/tos` but rendered identical shell content. Same limitation: content unread. No user accounts: As a read-only mempool viewer, there is no signup flow, no account system, and no custody of user funds. This is a public utility, not a wallet. Data transparency: Mempool explorers sit at an interesting trust intersection: the data they show is public (any Monero node can compute the same mempool state), but the *selection and ordering* of which transactions to display and which fee bands to recommend is operator-controlled. A malicious explorer could bias fee recommendations toward higher tiers or filter out transactions.

Operational specs. Architecture: SPA (single-page application), All content lives behind hash routes. No public API surface — the page interacts with its data source internally. No Tor mirror: No onion address advertised and no `Onion-Location` header detected. Clearnet-only. A Tor-accessible mempool explorer is valuable for Monero users who route all traffic through Tor. Pricing: Free — mempool explorers are read-only public infrastructure and not typically monetised. No fee or donation prompt was visible in the shell or hash-route snippets. API surface: No public programmatic API. The shell hash route `#/api` exists but renders the same mempool-data shell as the homepage — informational only. Location / jurisdiction: Not published. The `.org` domain and Monero-only focus suggest a community or privacy-advocacy project, but this is inference without source material. Domain: `monerospace.org` — the `.org` TLD is the strongest non-geographic trust signal among gTLDs, typically associated with non-profit or community projects. The name is a clear reference to the Bitcoin mempool.space.

Grade rationale. Listed at Grade B because the tool demonstrably works — the homepage shell renders live Monero mainnet mempool data with block heights, pool attribution, and fee estimation bands (operator-published). That is the core function of a mempool explorer, and a public audit confirms it is operational. Grade A is withheld because: (1) zero peer-directory matches — the tool is undiscovered; (2) the privacy policy and terms pages exist as hash routes but render identical shell content, leaving the operator's logging and data-retention posture unread; (3) no Tor mirror; (4) no operator background or jurisdiction. Among Monero infrastructure tools in this directory, a published privacy policy (logging posture: do they record IPs/queries/mempool snapshots?) and a Tor mirror would raise this to Grade A.

Caveats. The SPA rendered identical 3101-byte shell content on all 38 returning paths and all hash routes — live mempool data was captured (confirming functionality) but the privacy/about/terms/FAQ pages are confirmed to exist as routes with zero unique text extracted. The SPA likely requires extended JavaScript hydration to expose hash-route content. include There is no custody and no signup flow. Mempool explorers are an under-appreciated trust surface: they control which transactions are displayed, in what order, and what fee rates are recommended. A compromised or malicious explorer could bias fee estimation, censor specific transactions, or selectively omit mempool entries — and end users have no way to detect this without running their own node. This is not unique to MoneroSpace (it applies to all hosted mempool explorers) but it should be stated in the review.