SiaMining


ab5cac3efac68dd722febf23f70b0cd2f8efcba7da969d21ff0952d11c1192042bddbe56b406

Statistics

Unpaid Balance
130.15 SC
All-Time Rewards
593,972.84 SC
All-Time Hashes
17,557 PH
Blocks Found
5
Last Share
20:33:04 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 806 GH/s 14,417,920 0 (0.0%) 0 (0.0%) 0.73 SC
15 min 528 GH/s 28,311,552 0 (0.0%) 0 (0.0%) 1.44 SC
60 min 458 GH/s 98,304,000 0 (0.0%) 0 (0.0%) 5.02 SC
6 hours 483 GH/s 621,281,280 0 (0.0%) 1,835,008 (0.3%) 31.56 SC
24 hours 489 GH/s 2,520,514,560 0 (0.0%) 6,553,600 (0.3%) 126.63 SC

Workers (1/1)

Last refreshed: 20:33:09 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
Centaurjust now
Stratum
806 GH/s
0.0% stale
528 GH/s
0.0% stale
458 GH/s
0.0% stale
483 GH/s
0.0% stale
489 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-05-11 19:55 UTC 501.07 SC 04a697cd2303f2ca... confirmed
2021-05-08 02:55 UTC 500.76 SC 18ce0bf70f61a784... confirmed
2021-05-05 07:10 UTC 500.97 SC 84e68e1d567f4264... confirmed
2021-05-02 08:40 UTC 500.49 SC 1d808a6248b0b2b8... confirmed
2021-04-28 21:40 UTC 501.04 SC dee3492373345279... confirmed
2021-04-25 05:25 UTC 500.26 SC 8b6587d5d6bedab8... confirmed
2021-04-21 10:55 UTC 501.27 SC baf4ac609edb8286... confirmed
2021-04-18 01:25 UTC 500.27 SC 0a3528b08722c7ab... confirmed
2021-04-14 15:40 UTC 501.11 SC 6f5116f554e76a00... confirmed
Show more...

All-Time Paid Out: 593,842.69 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.