SiaMining


4f200321ac9aa925dfbbf72589bdff0166cfca0bf0c85af73bda34c864e1b887699f0d40d951

Statistics

Unpaid Balance
182.61 SC
All-Time Rewards
1,345,316.04 SC
All-Time Hashes
33,546 PH
Blocks Found
31
Last Share
14:05:15 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 660 GH/s 11,796,480 0 (0.0%) 0 (0.0%) 1.08 SC
15 min 567 GH/s 30,408,704 0 (0.0%) 0 (0.0%) 2.80 SC
60 min 573 GH/s 122,945,536 0 (0.0%) 262,144 (0.2%) 11.29 SC
6 hours 570 GH/s 734,003,200 262,144 (0.0%) 1,048,576 (0.1%) 66.94 SC
24 hours 596 GH/s 3,068,395,520 262,144 (0.0%) 21,495,808 (0.7%) 275.27 SC

Workers

No workers defined.

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-10-23 22:25 UTC 501.68 SC 340bc97dfd7087cf... confirmed
2020-10-22 01:10 UTC 500.97 SC 36368368475cae45... confirmed
2020-10-20 11:55 UTC 501.93 SC 90ec42542e80a75a... confirmed
2020-10-18 16:40 UTC 501.09 SC 4f5c9e7dbd64d568... confirmed
2020-10-17 00:25 UTC 500.31 SC 22c8e327f7abd347... confirmed
2020-10-15 10:40 UTC 501.36 SC 67b91ca047f62c7a... confirmed
2020-10-13 07:10 UTC 501.48 SC 8f2aed4c21e18388... confirmed
2020-10-11 12:40 UTC 500.69 SC c2d6056a25562b92... confirmed
2020-10-09 17:10 UTC 502.40 SC 588ae644cbe2807f... confirmed
2020-10-07 22:40 UTC 500.56 SC e0c05c2120db4365... confirmed
2020-10-06 04:55 UTC 503.17 SC d43edc590e3dcd44... confirmed
2020-10-04 09:40 UTC 501.71 SC 8d2102568cb5c4c5... confirmed
2020-10-02 12:40 UTC 501.53 SC c3d1cba86352d4f9... confirmed
2020-09-30 17:25 UTC 502.72 SC 0a7639cc34d263db... confirmed
2020-09-28 22:25 UTC 500.05 SC 806e8a73802a7e4d... confirmed
2020-09-27 02:25 UTC 502.60 SC 6151ae83dd437d0b... confirmed
2020-09-25 05:40 UTC 501.39 SC 6678d4392be9eeb1... confirmed
Show more...

All-Time Paid Out: 1,345,133.43 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.