02f134fc290c4c9b33eb115653a4e053ad21a433f4d044a1a257cffa96813b0157afcf6947d5
Statistics
- Unpaid Balance
- 481.50 SC
- All-Time Rewards
- 16,781.58 SC
- All-Time Hashes
- 8,794 PH
- Blocks Found
- 1
- Last Share
- 19:38:00 UTC
(just now)
| Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
|---|---|---|---|---|---|
| 5 min | 4,907 GH/s | 87,752,704 | 0 (0.0%) | 0 (0.0%) | 2.83 SC |
| 15 min | 4,876 GH/s | 261,554,176 | 0 (0.0%) | 0 (0.0%) | 8.45 SC |
| 60 min | 4,632 GH/s | 993,984,512 | 0 (0.0%) | 0 (0.0%) | 32.19 SC |
| 6 hours | 4,615 GH/s | 5,940,346,880 | 1,310,720 (0.0%) | 0 (0.0%) | 193.78 SC |
| 24 hours | 4,552 GH/s | 23,413,833,728 | 28,180,480 (0.1%) | 0 (0.0%) | 742.86 SC |
Workers (4/4)
Last refreshed: 19:38:02 UTC (just now)
| Name | Last Share | 5 minutes | 15 minutes | 1 hour | 6 hours | 24 hours |
|---|---|---|---|---|---|---|
| blfc01 | just now Stratum | 3,167 GH/s 0.0% stale | 3,137 GH/s 0.0% stale | 2,969 GH/s 0.0% stale | 2,986 GH/s 0.0% stale | 2,947 GH/s 0.1% stale |
| blfc02 | just now Stratum | 627 GH/s 0.0% stale | 566 GH/s 0.0% stale | 524 GH/s 0.0% stale | 542 GH/s 0.0% stale | 538 GH/s 0.2% stale |
| blfc03 | 48 sec ago Stratum | 513 GH/s 0.0% stale | 586 GH/s 0.0% stale | 567 GH/s 0.0% stale | 531 GH/s 0.0% stale | 536 GH/s 0.1% stale |
| blfc04 | just now Stratum | 572 GH/s 0.0% stale | 572 GH/s 0.0% stale | 573 GH/s 0.0% stale | 556 GH/s 0.1% stale | 531 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.
All-Time Paid Out: 16,300.07 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.