SiaMining


1b053962d18a4ad8c778957af096ccf22119fc0a368419385f730cabef0606ba12bb57443c07

Statistics

Unpaid Balance
275.54 SC
All-Time Rewards
17,802.74 SC
All-Time Hashes
14,937 PH
Blocks Found
1
Last Share
01:42:07 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 1,407 GH/s 25,165,824 0 (0.0%) 0 (0.0%) 0.65 SC
15 min 1,671 GH/s 89,653,248 0 (0.0%) 0 (0.0%) 2.33 SC
60 min 1,495 GH/s 320,733,184 0 (0.0%) 0 (0.0%) 8.27 SC
6 hours 1,503 GH/s 1,934,491,648 0 (0.0%) 0 (0.0%) 50.58 SC
24 hours 1,491 GH/s 7,678,394,368 0 (0.0%) 0 (0.0%) 196.86 SC

Workers (1/1)

Last refreshed: 01:42:22 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
scboxjust now
Stratum
1,407 GH/s
0.0% stale
1,671 GH/s
0.0% stale
1,495 GH/s
0.0% stale
1,503 GH/s
0.0% stale
1,491 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
2024-05-03 16:10 UTC 501.84 SC 4f813ee1c6df35ab... confirmed
2024-05-01 01:10 UTC 501.18 SC 57fdda1ec75d9d32... confirmed
2024-04-27 11:10 UTC 500.49 SC 30442b392a013c53... confirmed
2024-04-24 08:40 UTC 500.38 SC 472fa1e9e7ab519e... confirmed
2024-04-20 13:40 UTC 501.06 SC b9e9e27e29a8090a... confirmed
2024-04-17 00:40 UTC 500.37 SC 6b9e3e909f6f1ae7... confirmed
2024-04-13 17:40 UTC 501.05 SC f4eb27cbffb6997a... confirmed
2024-04-10 12:10 UTC 500.29 SC 411d454815f4e5a8... confirmed
2024-04-07 09:40 UTC 501.31 SC 75b08ef2fd1fa42b... confirmed
Show more...

All-Time Paid Out: 17,527.20 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.