SiaMining


a7fed3f51f9dcce17cc738c79475832a49c22a22fa42232d699c0cb7f3f59bfae4625b7ce33b

Statistics

Unpaid Balance
98.21 SC
All-Time Rewards
13,632.20 SC
All-Time Hashes
2,656 PH
Blocks Found
1
Last Share
21:06:06 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 323 GH/s 5,767,168 0 (0.0%) 0 (0.0%) 0.41 SC
15 min 406 GH/s 21,757,952 0 (0.0%) 0 (0.0%) 1.56 SC
60 min 367 GH/s 78,643,200 0 (0.0%) 0 (0.0%) 5.67 SC
6 hours 398 GH/s 512,753,664 0 (0.0%) 786,432 (0.2%) 36.60 SC
24 hours 397 GH/s 2,043,936,768 262,144 (0.0%) 5,242,880 (0.3%) 143.04 SC

Workers (1/1)

Last refreshed: 21:06:14 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
obeliskjust now
Stratum
323 GH/s
0.0% stale
406 GH/s
0.0% stale
367 GH/s
0.0% stale
398 GH/s
0.0% stale
397 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
2021-03-08 04:55 UTC 500.95 SC cd554c8c0778f0a3... confirmed
2021-03-04 20:55 UTC 501.07 SC 780cc171e2e8b59a... confirmed
2021-03-01 13:25 UTC 501.35 SC f2abd781840c2a58... confirmed
2021-02-26 10:40 UTC 500.31 SC 866d84f00f4e5442... confirmed
2021-02-23 01:55 UTC 501.47 SC 3defe37ef6e3ceb3... confirmed
2021-02-20 00:10 UTC 500.37 SC 649b2a05d2c62c08... confirmed
2021-02-16 12:55 UTC 500.37 SC ce4db4757ac79aac... confirmed
2021-02-12 17:10 UTC 500.30 SC 3ea02fd36995917b... confirmed
2021-02-08 19:55 UTC 276.74 SC 417a56e7170b30ca... confirmed
Show more...

All-Time Paid Out: 13,533.98 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.