IMPORTANT: This mining pool will be shut down on May 1, 2025 (in 66 days). Please migrate your miners to another pool by that date.
8b943b0b1c1b1f9b57af9d05aa1f0e2bce52d276f02f2cc9319e88f073972eb7e1d2a476c7bf
Statistics
- Unpaid Balance
- 405.18 SC
- All-Time Rewards
- 36,410.23 SC
- All-Time Hashes
- 35,995 PH
- Blocks Found
- 1
- Last Share
- 14:41:43 UTC
(just now)
| Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
|---|---|---|---|---|---|
| 5 min | 4,750 GH/s | 84,934,656 | 0 (0.0%) | 0 (0.0%) | 1.56 SC |
| 15 min | 4,506 GH/s | 241,696,768 | 0 (0.0%) | 0 (0.0%) | 4.44 SC |
| 60 min | 4,877 GH/s | 1,046,478,848 | 0 (0.0%) | 0 (0.0%) | 19.14 SC |
| 6 hours | 4,867 GH/s | 6,246,612,992 | 19,398,656 (0.3%) | 0 (0.0%) | 110.57 SC |
| 24 hours | 4,833 GH/s | 24,819,920,896 | 68,157,440 (0.3%) | 1,572,864 (0.0%) | 426.87 SC |
Workers (3/3)
Last refreshed: 14:41:47 UTC (just now)
| Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
|---|---|---|---|---|---|---|
| 1 | just now Stratum | 645 GH/s 0.0% stale | 831 GH/s 0.0% stale | 909 GH/s 0.0% stale | 921 GH/s 0.3% stale | 918 GH/s 0.3% stale |
| 4 | just now Stratum | 2,463 GH/s 0.0% stale | 1,886 GH/s 0.0% stale | 1,989 GH/s 0.0% stale | 2,000 GH/s 0.2% stale | 1,957 GH/s 0.3% stale |
| 5 | just now Stratum | 1,613 GH/s 0.0% stale | 1,789 GH/s 0.0% stale | 1,979 GH/s 0.0% stale | 1,946 GH/s 0.4% stale | 1,958 GH/s 0.3% 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: 36,005.04 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.