SiaMining


182195e70b67c129b859d1728b6ae7e9b48d0761c584beefffc55e0663f927613a56089c7b54

Statistics

Unpaid Balance
474.85 SC
All-Time Rewards
745,460.26 SC
All-Time Hashes
23,106 PH
Blocks Found
21
Last Share
10:51:42 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 367 GH/s 6,553,600 0 (0.0%) 0 (0.0%) 0.58 SC
15 min 479 GH/s 25,690,112 0 (0.0%) 0 (0.0%) 2.30 SC
60 min 454 GH/s 97,517,568 0 (0.0%) 0 (0.0%) 8.81 SC
6 hours 495 GH/s 637,534,208 0 (0.0%) 262,144 (0.0%) 58.11 SC
24 hours 511 GH/s 2,629,304,320 262,144 (0.0%) 6,291,456 (0.2%) 232.65 SC

Workers (1/1)

Last refreshed: 10:51:46 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
SC1_Minerjust now
Stratum
367 GH/s
0.0% stale
479 GH/s
0.0% stale
454 GH/s
0.0% stale
495 GH/s
0.0% stale
511 GH/s
0.0% stale

Recent Payouts

Payouts are performed daily with a threshold of 500 SC, or up to every 6 hours when over 1000 SC.

Date/TimeAmountTransaction IDStatus
2020-08-08 08:40 UTC 501.48 SC eb8972f4bb010cd4... confirmed
2020-08-06 05:40 UTC 501.79 SC 06c402a1c7f03ad5... confirmed
2020-08-04 02:40 UTC 501.91 SC dd6fdbb3ee74da17... confirmed
2020-08-01 22:25 UTC 500.90 SC 4d9faa021c2b4b44... confirmed
2020-07-30 16:40 UTC 502.05 SC 376e213c526fdee7... confirmed
2020-07-28 13:10 UTC 500.97 SC 8edb3133b8e67b35... confirmed
2020-07-26 08:40 UTC 500.54 SC 80fb7ba722591ac9... confirmed
2020-07-24 02:25 UTC 501.36 SC 52e3914f354ca23d... confirmed
2020-07-21 18:10 UTC 501.42 SC 8f59ef0b602e8f66... confirmed
2020-07-19 14:55 UTC 502.24 SC 0148c995c6753b6b... confirmed
2020-07-17 14:40 UTC 502.07 SC 9e017c41e8691fb9... confirmed
2020-07-15 08:25 UTC 502.74 SC 252bcaa588b87185... confirmed
2020-07-13 03:40 UTC 500.06 SC 47e20d9a6a773327... confirmed
Show more...

All-Time Paid Out: 744,985.41 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.