SiaMining


84419528a0f1035c52903ec621e424e7bb94ab3bb169f5242455c512a6568c567848ec2bc9ba

Statistics

Unpaid Balance
360.62 SC
All-Time Rewards
21,412.04 SC
All-Time Hashes
7,492 PH
Blocks Found
3
Last Share
17:01:31 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 880 GH/s 15,728,640 0 (0.0%) 0 (0.0%) 0.81 SC
15 min 916 GH/s 49,152,000 0 (0.0%) 0 (0.0%) 2.53 SC
60 min 1,048 GH/s 224,788,480 0 (0.0%) 0 (0.0%) 11.48 SC
6 hours 953 GH/s 1,226,244,096 65,536 (0.0%) 0 (0.0%) 61.48 SC
24 hours 924 GH/s 4,755,292,160 589,824 (0.0%) 524,288 (0.0%) 228.85 SC

Workers

No workers defined.

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.

Date/TimeAmountTransaction IDStatus
2023-01-26 02:40 UTC 500.74 SC 8c82a2ffa956541f... confirmed
2023-01-23 19:25 UTC 500.28 SC 9bc2b4390a77480b... confirmed
2023-01-21 11:55 UTC 500.59 SC d6b6e2a82576f85d... confirmed
2023-01-19 04:25 UTC 500.81 SC 20ea1a63031f169b... confirmed
2023-01-16 14:40 UTC 501.17 SC 8c9a2c8dd5dcb1ea... confirmed
2023-01-14 08:25 UTC 501.51 SC 4c9f0ffb615d5e01... confirmed
2023-01-12 04:40 UTC 502.26 SC e5702b2f154792a1... confirmed
2023-01-09 20:55 UTC 500.72 SC cd6a108cb352145a... confirmed
2023-01-07 10:40 UTC 501.91 SC 935719baa4569a65... confirmed
2023-01-05 01:40 UTC 501.37 SC 48cbb2e3ffc64d56... confirmed
2023-01-02 16:55 UTC 500.86 SC fd0e8187828d2ab6... confirmed
2022-12-31 07:40 UTC 500.66 SC a6478e133b8a1a3b... confirmed
2022-12-29 00:55 UTC 500.18 SC 78f2e4db95d0a0a0... confirmed
Show more...

All-Time Paid Out: 21,051.42 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.