MONZEROGet started

YOUR POOL ACTIVITY

Follow your mining.

Look up pool-reported activity for your public mining address. This does not reveal your wallet’s private balance or transaction history.

Your address is sent to Monzero’s website and mining pool for this lookup. It is not added to the page URL or saved in browser storage. The pool’s upstream lookup uses an address query, which its server may log. Do not enter seed words or private keys.

Latest pool observation

Enter your address to begin. No lookup has been made.

Source: Monzero Pool. Hashrate is estimated from accepted work over ten minutes, not an instantaneous CPU measurement. Pool contribution compares separately sampled estimates. A zero result does not prove that an address has mined here.

Workers currently connected

Labels stay in memory unless you opt in.

Labels are your own notes, not worker identities verified by the pool. Connections sharing a pool login share a label; numbering can change. Saved labels stay on this device until forgotten, including on shared computers. Clear dashboard and switching saved labels off also remove them. Raw login names and mining addresses are not saved with them, but someone using this device can match labels by looking up the same address. If the server resets its identifier key, saved labels will need to be assigned again.

Manage saved labels, including disconnected workers

    No observation yet.

    Pool-reported payments

    Up to 50 recent payments marked sent by the pool. Confirmation counts are unavailable here; inspect a transaction in the explorer. Payment timestamps are pool record times, not confirmation times. This list does not expose other wallet transactions.

    Observations during this visit

    Off by default. Successful lookups add samples after you enable this option; repeated or earlier website retrieval timestamps are skipped. No additional requests are made. Up to 120 observations are retained; unchecking this option, changing the address, clearing the dashboard or closing the page removes them. This is not historical pool data.

    Session charts are off.

    Pending rewards can fall when the pool records a payout or changes its accounting. They are not cumulative earnings. Chart amounts are approximate; the observation table preserves exact pool amounts. Gaps indicate failed lookups, unavailable metrics or more than 90 seconds between observations. Lines between samples are visual guides, not extra measurements. Consecutive ten-minute hashrate averages overlap; they are not independent minute-by-minute measurements.

    Alerts during this visit

    Alerts are off.

    Payment alerts are off.

    Browser notifications are off.

    Alerts use your existing lookups; enable the separate one-minute refresh option for periodic checks while this tab is visible. Automatic refresh pauses while editing a worker label or when the tab is hidden. Monitoring stops when this page closes; already displayed notifications may remain in your notification center. Hashrate, worker-count and lookup-failure conditions must occur on two observations at least 30 seconds apart and no more than 90 seconds apart. A continuing condition alerts once; after recovery, repeats are limited to one per condition every ten minutes and may be delayed until the cooldown ends. Unknown readings interrupt the consecutive count. Up to 20 alerts are kept in memory.

    The hashrate baseline is the first positive reading after enabling alerts. Changing thresholds requires enabling again, which resets the baseline. Worker-count alerts do not identify individual machines. Lookup failures can be caused by your connection, rate limits or the website, not only the pool. Changing the address, clearing the dashboard or stopping alerts clears monitoring. Browser notifications require a separate opt-in and contain no address, label or amount, but reveal that you use mining monitoring. Browser permission can remain granted until revoked in browser settings.

    Payment alerts are optional. The first available payment list becomes a baseline without alerts. Later newly observed transaction IDs trigger at most one payment alert per ten minutes; additional payments are grouped until a subsequent successful lookup after that interval. This does not establish when a payment was actually sent or confirmed. If the pool initially returns incomplete history, older payments that appear later can trigger an alert. Missing or invalid lists are skipped; grouped alerts wait for a valid list. The pool returns up to 50 payments, so payments between visits or during long gaps may be missed. Payment monitoring pauses after 1,000 distinct payment IDs, including any queued alerts; re-enable alerts to start a fresh baseline. IDs are retained only in memory.

    History and unavailable metrics

    The pool does not currently provide historical hashrate, accepted/rejected share totals or worker uptime through its public API. Earlier historical charts are unavailable; session charts contain only observations collected here after opting in. Optional local worker labels are available above.