SiaMining


501d300c90c382b21b72b6510128087bb5847414da5f975ad33cbefaba333407db6d137122c0

Statistics

Unpaid Balance
0.00 SC
All-Time Rewards
250,860.59 SC
All-Time Hashes
156,822 PH
Blocks Found
15
Last Share
03:42:26 UTC
(1 week ago)

Not currently mining.

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
2024-04-21 19:55 UTC 178.39 SC 333b32659e59c640... confirmed
2024-04-16 19:55 UTC 590.22 SC 84c91fc0be18d264... confirmed
2024-04-15 19:55 UTC 502.83 SC fbb381b252747f02... confirmed
2024-04-14 10:25 UTC 354.08 SC 4f1d923ad7230ad1... confirmed
2024-04-09 10:25 UTC 581.73 SC c5db4c62c197c1ef... confirmed
2024-04-08 10:25 UTC 667.81 SC 53b920a99a28c832... confirmed
2024-04-07 10:25 UTC 641.40 SC e89d83bf3f79f17c... confirmed
2024-04-06 10:25 UTC 629.20 SC a651603247dc127b... confirmed
2024-04-05 10:25 UTC 619.19 SC 340dd898f389a0ff... confirmed
2024-04-04 10:25 UTC 695.54 SC 645a5a68c43c14d4... confirmed
2024-04-03 10:25 UTC 642.56 SC f873be526e46622c... confirmed
2024-04-02 10:25 UTC 588.34 SC c7ed21afac725cba... confirmed
2024-04-01 10:25 UTC 512.46 SC 9aac853bfb094eee... confirmed
2024-03-31 10:25 UTC 500.52 SC 9bf59ed46db17431... confirmed
2024-03-30 09:10 UTC 559.46 SC 01c59799e85e6833... confirmed
2024-03-29 09:10 UTC 567.27 SC f7c226daecb9ce87... confirmed
2024-03-28 09:10 UTC 552.25 SC 251788744f4cbd4a... confirmed
2024-03-27 09:10 UTC 577.00 SC bb1d225dd8a361f5... confirmed
Show more...

All-Time Paid Out: 250,860.59 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.