SiaMining


cceaa3c520cbb7c5fe0d62e844de582fb9d8b217b035f74d78d7baeaa8330bf7b9c6521a33ba

Statistics

Unpaid Balance
146.04 SC
All-Time Rewards
363,882.03 SC
All-Time Hashes
21,977 PH
Blocks Found
8
Last Share
23:27:29 UTC
(just now)
Hash Rate Valid Shares Stale Shares Invalid Shares Rewards
5 min 484 GH/s 8,650,752 0 (0.0%) 0 (0.0%) 0.72 SC
15 min 425 GH/s 22,806,528 0 (0.0%) 0 (0.0%) 1.90 SC
60 min 443 GH/s 95,158,272 0 (0.0%) 0 (0.0%) 7.91 SC
6 hours 464 GH/s 596,901,888 524,288 (0.1%) 3,145,728 (0.5%) 50.34 SC
24 hours 472 GH/s 2,429,812,736 1,310,720 (0.1%) 6,815,744 (0.3%) 205.67 SC

Workers (1/1)

Last refreshed: 23:27:52 UTC (just now)

Name Last Share 5 minutes 15 minutes 1 hour 6 hours 24 hours
cryptocableMTjust now
Stratum
484 GH/s
0.0% stale
425 GH/s
0.0% stale
443 GH/s
0.0% stale
464 GH/s
0.5% invalid
472 GH/s
0.1% stale

Recent Payouts

Payouts are performed daily with a threshold of 500 SC, or up to every 6 hours when over 1000 SC.

Date/TimeAmountTransaction IDStatus
2021-01-23 06:25 UTC 501.64 SC 91bf81bd7a451454... confirmed
2021-01-20 21:10 UTC 502.11 SC 7ab4aeb6d8bbcbb0... confirmed
2021-01-18 08:10 UTC 501.87 SC 35a9cf69605ed7ce... confirmed
2021-01-16 01:10 UTC 502.20 SC c8dcf05f6accb216... confirmed
2021-01-13 20:10 UTC 502.22 SC 3f75963bfe748c5b... confirmed
2021-01-11 10:40 UTC 500.68 SC a3961ed277689027... confirmed
2021-01-08 20:55 UTC 500.23 SC 0cc33cd609eadae7... confirmed
2021-01-06 08:25 UTC 501.29 SC 1f987ef3c99149b6... confirmed
2021-01-04 00:55 UTC 501.99 SC 20ee49fc445b4eef... confirmed
2021-01-01 13:10 UTC 501.04 SC 70e53dc8f9b1b6e4... confirmed
2020-12-30 01:10 UTC 500.86 SC 16dfe31754cbe2c5... confirmed
2020-12-27 13:55 UTC 503.66 SC ea75df19272b0ab5... confirmed
2020-12-25 06:10 UTC 502.02 SC 409f9c57cee428c2... confirmed
Show more...

All-Time Paid Out: 363,735.99 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.