SiaMining


3f7a95ec3dabcbfe8b574b848812746041fd261c2ff801dccc978cc97b32a9b9fda9c0e6089b

Statistics

Unpaid Balance
277.54 SC
All-Time Rewards
156,791.10 SC
All-Time Hashes
97,213 PH
Blocks Found
4
Last Share
06:09:17 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 3,841 GH/s 68,681,728 0 (0.0%) 0 (0.0%) 1.33 SC
15 min 3,733 GH/s 200,278,016 0 (0.0%) 0 (0.0%) 3.89 SC
60 min 3,802 GH/s 815,792,128 0 (0.0%) 0 (0.0%) 16.00 SC
6 hours 3,929 GH/s 5,058,330,624 524,288 (0.0%) 0 (0.0%) 100.13 SC

Workers (1/1)

Last refreshed: 06:09:23 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
002just now
Stratum
1,964 GH/s
0.0% stale
1,886 GH/s
0.0% stale
1,876 GH/s
0.0% stale
1,960 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.

Date/TimeAmountTransaction IDStatus
2025-02-02 13:25 UTC 317.66 SC db4f0b9dab911a6e... confirmed
2025-01-28 13:25 UTC 147.10 SC 6a695134cba663db... confirmed
2025-01-23 13:25 UTC 501.71 SC 58e3eb2bbf217916... confirmed
2025-01-18 14:40 UTC 501.54 SC 2de04d58b0c63e18... confirmed
2025-01-17 01:25 UTC 501.85 SC 2058a827e4bf9736... confirmed
2025-01-15 10:10 UTC 501.19 SC eb117270d20f8542... confirmed
2025-01-13 09:25 UTC 500.12 SC 47537fefdde69b75... confirmed
2025-01-11 17:40 UTC 500.55 SC 1a4bb394386146c0... confirmed
2025-01-10 04:40 UTC 500.78 SC a83ebb90c26081f7... confirmed
2025-01-08 15:25 UTC 500.87 SC 3e306162c73bf3c0... confirmed
Show more...

All-Time Paid Out: 156,513.55 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.