IMPORTANT: This mining pool will be shut down on May 1, 2025 (in 11 days). Please migrate your miners to another pool by that date.
4f7858f0327f6f014dd0ed1d51ed085f1912092a3fa45b8361cadf63e8365c5cc68ca236eee3
Statistics
- Unpaid Balance
- 39.42 SC
- All-Time Rewards
- 208,182.10 SC
- All-Time Hashes
- 116,112 PH
- Blocks Found
- 4
- Last Share
- 18:39:59 UTC
(just now)
| Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
|---|---|---|---|---|---|
| 5 min | 1,422 GH/s | 25,427,968 | 0 (0.0%) | 0 (0.0%) | 0.54 SC |
| 15 min | 1,544 GH/s | 82,837,504 | 0 (0.0%) | 0 (0.0%) | 1.77 SC |
| 60 min | 1,530 GH/s | 328,302,592 | 0 (0.0%) | 0 (0.0%) | 7.04 SC |
| 6 hours | 1,492 GH/s | 1,920,565,248 | 0 (0.0%) | 0 (0.0%) | 41.31 SC |
| 24 hours | 1,455 GH/s | 7,494,008,832 | 0 (0.0%) | 655,360 (0.0%) | 160.21 SC |
Workers (3/3)
Last refreshed: 18:40:00 UTC (just now)
| Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
|---|---|---|---|---|---|---|
| 001 | just now Stratum | 425 GH/s 0.0% stale | 484 GH/s 0.0% stale | 494 GH/s 0.0% stale | 465 GH/s 0.0% stale | 446 GH/s 0.0% stale |
| 002 | just now Stratum | 396 GH/s 0.0% stale | 479 GH/s 0.0% stale | 501 GH/s 0.0% stale | 479 GH/s 0.0% stale | 473 GH/s 0.0% stale |
| 004 | just now Stratum | 557 GH/s 0.0% stale | 582 GH/s 0.0% stale | 535 GH/s 0.0% stale | 547 GH/s 0.0% stale | 537 GH/s 0.0% stale |
Recent Payouts
Reminder: Due to Sia's Foundation hardfork, you must upgrade your Sia wallet software to version 1.5.4 or higher. You can continue to use the same address for mining, and no changes to your configuration are needed. For more information about the fork, click here.
Payouts are performed daily with a threshold of 500 SC, or up to every 6 hours when over 1000 SC.
All-Time Paid Out: 208,142.68 SC
Note: If you have not received one of the payout transactions listed above, please click on the transaction ID to look it up on the Explorer. If the transaction appears there, it is proof that it went through successfully, and that the problem is with the receiving end. If you are using an exchange address, you should contact the exchange.