SiaMining


b34d342c24757b0b84a140d9b227d83af1e451b32a910e0ce96af069611818c677f10eb0e9f3

Statistics

Unpaid Balance
336.69 SC
All-Time Rewards
14,271.50 SC
All-Time Hashes
11,895 PH
Blocks Found
1
Last Share
17:05:17 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 1,012 GH/s 18,087,936 0 (0.0%) 0 (0.0%) 0.34 SC
15 min 889 GH/s 47,448,064 262,144 (0.5%) 0 (0.0%) 0.91 SC
60 min 767 GH/s 164,364,288 262,144 (0.2%) 262,144 (0.2%) 3.20 SC
6 hours 929 GH/s 1,195,311,104 1,048,576 (0.1%) 2,621,440 (0.2%) 24.41 SC
24 hours 946 GH/s 4,866,736,128 4,358,144 (0.1%) 4,456,448 (0.1%) 101.45 SC

Workers (2/2)

Last refreshed: 17:05:22 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
worker1just now
Stratum
469 GH/s
0.0% stale
440 GH/s
1.1% stale
313 GH/s
0.4% stale
450 GH/s
0.1% stale
464 GH/s
0.1% stale
worker2just now
Stratum
513 GH/s
0.0% stale
450 GH/s
0.0% stale
454 GH/s
0.0% stale
480 GH/s
0.0% stale
482 GH/s
0.1% 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-06-21 09:10 UTC 387.08 SC fbe08ecbe35cd922... confirmed
2024-06-16 09:10 UTC 331.95 SC f6430a09d00c769d... confirmed
2024-06-11 09:10 UTC 445.67 SC 93ba462f0337f55e... confirmed
2024-06-06 09:10 UTC 432.36 SC f2458d59e0040630... confirmed
2024-06-01 09:10 UTC 500.95 SC 8c99c7d5683dbb19... confirmed
2024-05-27 10:10 UTC 500.49 SC 69d7a2882ec46917... confirmed
Show more...

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