SiaMining


91d671576a4402bad18ee8b8efed9e46b51d17e59e99e0001ea3d4276540ea57b32e85076e1c

WARNING: This address has been inactive for 5 days. After 30 days of inactivity, an account may be reset, and any accrued balance forfeited as per the Terms of Service.

Statistics

Unpaid Balance
0.55 SC
All-Time Rewards
801,491.81 SC
All-Time Hashes
46,546 PH
Blocks Found
19
Last Share
17:42:45 UTC
(5 days ago)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
60 min 0.0 MH/s 0 0 (0.0%) 0 (0.0%) 0.00 SC
6 hours 0.0 MH/s 0 0 (0.0%) 0 (0.0%) 0.00 SC
24 hours 0.0 MH/s 0 0 (0.0%) 0 (0.0%) 0.00 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
2021-05-07 17:40 UTC 502.14 SC a0ca7e570149fcbf... confirmed
2021-05-06 06:25 UTC 503.10 SC 037933234f952fbb... confirmed
2021-05-04 17:40 UTC 501.39 SC cc0c6a8dffb6bf36... confirmed
2021-05-03 00:55 UTC 501.01 SC cc039e630d75a256... confirmed
2021-05-01 00:10 UTC 502.64 SC 4a4d78126387082b... confirmed
2021-04-29 04:25 UTC 502.41 SC 638e5371daccf193... confirmed
2021-04-27 03:55 UTC 501.51 SC 4194bffd83aa50f8... confirmed
2021-04-25 05:25 UTC 502.63 SC 8b6587d5d6bedab8... confirmed
2021-04-23 04:40 UTC 501.42 SC e922b5df8fd18048... confirmed
2021-04-21 09:10 UTC 503.39 SC 0d143a402f8c1c4e... confirmed
2021-04-17 23:55 UTC 495.30 SC 4a8b14a7538178b3... confirmed
2021-04-12 23:55 UTC 501.01 SC 8fb3d863ae1162ab... confirmed
Show more...

All-Time Paid Out: 801,491.26 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.