f6152df1edb6f61f6daa48edaf50f495224503f7d3af8925bdba0076f9fd12fd711b7e4920a0
Statistics
- Unpaid Balance
- 127.89 SC
- All-Time Rewards
- 268,848.35 SC
- All-Time Hashes
- 179,394 PH
- Blocks Found
- 12
- Last Share
- 08:07:07 UTC
(just now)
Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
---|---|---|---|---|---|
5 min | 5,160 GH/s | 92,274,688 | 0 (0.0%) | 0 (0.0%) | 1.74 SC |
15 min | 5,454 GH/s | 292,552,704 | 0 (0.0%) | 0 (0.0%) | 5.53 SC |
60 min | 5,562 GH/s | 1,193,410,560 | 0 (0.0%) | 0 (0.0%) | 22.64 SC |
6 hours | 5,704 GH/s | 7,341,015,040 | 3,145,728 (0.0%) | 0 (0.0%) | 140.45 SC |
24 hours | 5,698 GH/s | 29,330,243,584 | 12,058,624 (0.0%) | 524,288 (0.0%) | 565.38 SC |
Workers (4/4)
Last refreshed: 08:07:16 UTC (just now)
Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
---|---|---|---|---|---|---|
Ayra1 | just now Stratum | 2,492 GH/s 0.0% stale | 2,678 GH/s 0.0% stale | 2,861 GH/s 0.0% stale | 2,919 GH/s 0.0% stale | 2,942 GH/s 0.0% stale |
Munira1 | just now Stratum | 909 GH/s 0.0% stale | 958 GH/s 0.0% stale | 893 GH/s 0.0% stale | 910 GH/s 0.0% stale | 913 GH/s 0.1% stale |
Nuha1 | just now Stratum | 938 GH/s 0.0% stale | 938 GH/s 0.0% stale | 886 GH/s 0.0% stale | 923 GH/s 0.1% stale | 917 GH/s 0.0% stale |
Taima1 | just now Stratum | 821 GH/s 0.0% stale | 821 GH/s 0.0% stale | 921 GH/s 0.0% stale | 952 GH/s 0.0% stale | 926 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: 268,720.45 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.