DagCore · chain 1404
BlockDAG mining pool
Live pool status, every miner's hashrate, and a quick lookup for your own address. All data is updated directly from the DagCore mining pool.
Pool status
Why some blocks the pool found pay no reward
Rewards arrive straight into the pool wallet with no transaction, so they're counted from what actually lands: the BDAG that arrives, divided by a typical block reward.
Nothing is held back. A block the network doesn't reward pays nothing in, so there's nothing to split. The work still counts — those PPLNS credits are carried and split with the next reward that does arrive.
Pool hashrate
Chart data as a table
| Interval start | Hashrate | Shares |
|---|
Paid to miners per hour
BDAG, last 24 hChart data as a table
| Hour | Paid (BDAG) | Payouts |
|---|
Your wallet
Your name in the miner list
Connected as ·
A name is public. The miner list shows it next to the last four characters of your address, and every payment this pool has made to you is already visible on the chain — so a name can be connected to the address that carries it. Choose one you are comfortable being known by, or leave it blank and stay a four-character suffix.
Your wallet signs a short message to prove this address is yours. It costs nothing and sends no transaction — there is no account and no password. Your address stays visible in the list under the name, so anyone can still check a payout in the explorer. Disconnect forgets the wallet on this page and asks your wallet to drop this site's permission; reloading the page does not connect it again until you press Connect wallet.
| Status | — |
How this is worked out
| Total paid | — |
| PPLNS share | — |
| Last accepted share | — |
| Connected for | — |
Hashrate
How hashrate is estimated
Estimated from accepted shares: shares × the share difficulty the pool assigned × 65,536, per second. It is a statistical estimate — each point's noise is roughly 1/√(shares in it), so short intervals wobble more. Accepted work only: shares the pool rejected are not counted.
The bars count the shares your rig sent in each interval: accepted, and stale — sent for a job the pool had already replaced because the network moved on to a new block. Stale shares earn nothing; a few are normal, a large share of them points to a slow connection to the pool.
Chart data as a table
| Interval start | Hashrate | Accepted | Stale |
|---|
Payout history
| Time | Amount (BDAG) | Weight | Status | Transaction |
|---|
| Day | Payouts | Paid (BDAG) |
|---|
No payouts to summarise for this address yet.
Amounts are exactly what was sent. Confirmed after 12 confirmations.
Miners
| # | Miner | Hashrate · 10 min est. | Share | Status |
|---|
The window applies to this table and the Pool hashrate card together, so the rows add up to the card. Shorter windows are noisier: hashrate is estimated from accepted shares, and 10 minutes holds a sixth of an hour's shares, so luck moves it about 2.5 times as much.
About these columns
One row per address: this pool build rejects address.worker logins, so there are no per-machine names, and it reports device type as unknown, so there is no ASIC/GPU split. A miner can put a name on their address by connecting a wallet above and signing a message with the key that owns it — the address stays under the name, because that is what a payout is checked against in the explorer. Hashrate is estimated from accepted shares over the window chosen above (10 minutes, 1 hour or 24 hours), the same window as the Pool hashrate card; share is that hashrate as a part of the pool's. Earned is every confirmed payout. Waiting is what the address is owed and not yet paid: amounts from before (kept below the minimum, or about to be sent) plus, marked est., its share of block rewards that have arrived since the last payout. Mining = an accepted share in the last 5 min; idle = within the last hour; offline = longer. An address with no accepted share in the last 3 hours is not listed here — anything it is owed is still kept, and the lookup above still finds it.
Payout policy
PPLNS · 1% fee · paid every 5 min · minimum 1 BDAG, smaller amounts carried
- Scheme
- PPLNS — each block's reward is split by the pool's PPLNS weights at that block (pay per last N shares).
- Pool fee
- 1% of what actually arrives in the pool wallet.
- Payout frequency
- Every 5 minutes. The BDAG that arrived since the last payout, minus the fee, is divided by weight and sent.
- Minimum payout
- 1 BDAG. A smaller amount is kept and added to your next payout — it is not lost.
- Settlement
- Payouts are sent one at a time; each waits for 12 confirmations before the next.
- Paid from
- pool wallet
Why split what actually arrives?
The pool's own credit amounts are used only as weights between miners. The money that gets split is measured from the pool wallet's balance, so a payout can never promise more than was received.
What this page doesn't show
A per-worker list: this pool build rejects address.worker logins, so there are no worker names to list — only addresses, truncated in the miners table. Device type: the pool reports it as unknown for GPU miners, so there is no ASIC/GPU split. Accepted/rejected shares per wallet: the pool logs rejected shares without a wallet, so a per-wallet figure would really be pool-wide.