50565c15f5d479530bcbde8f5d15f95f48db9a472ce2eaa65ca644f66b86d60f81eafd2792c8
Statistics
- Unpaid Balance
- 4,855.05 mSCP
- All-Time Rewards
- 66,345.00 mSCP
- All-Time Hashes
- 1,807 PH
- Blocks Found
- 3
- Last Share
- 10:43:44 UTC
(just now)
Hash Rate | Valid Shares | Stale Shares | Invalid Shares | Rewards | |
---|---|---|---|---|---|
5 min | 4,750 GH/s | 84,934,656 | 0 (0.0%) | 0 (0.0%) | 51.93 mSCP |
15 min | 4,378 GH/s | 234,881,024 | 0 (0.0%) | 0 (0.0%) | 143.36 mSCP |
60 min | 4,255 GH/s | 913,047,552 | 0 (0.0%) | 0 (0.0%) | 553.71 mSCP |
6 hours | 4,201 GH/s | 5,408,423,936 | 0 (0.0%) | 0 (0.0%) | 3,350.74 mSCP |
24 hours | 4,116 GH/s | 21,196,046,336 | 3,145,728 (0.0%) | 0 (0.0%) | 13,401.62 mSCP |
Workers
No workers defined.
Recent Payouts
Payouts are performed daily with a threshold of 1000 mSCP, or up to every 6 hours when over 10000 mSCP.
Date/Time | Amount | Transaction ID | Status |
---|---|---|---|
2022-06-27 02:10 UTC | 10,127.79 mSCP | 97ae63f1c7e990a40b08ce33569bcf7f8f0a16e890a333e54c66bbd70acd37b2... | confirmed |
2022-06-26 07:55 UTC | 10,127.96 mSCP | cc9254841314a14c2c5ba9eac7622855eb1267cb5cc72b759f8240bc0ff13b6a... | confirmed |
2022-06-25 12:55 UTC | 10,007.93 mSCP | 23999af1f6f10a163a971f9d799dbc83c254cb627b3d4ce96b44306e7f0e0b7e... | confirmed |
2022-06-24 18:10 UTC | 10,081.66 mSCP | 9e96d16ae96e76f0f05698ba062cbf0b7e03cc173d353d7448407a8695016b3e... | confirmed |
2022-06-23 23:25 UTC | 10,019.01 mSCP | fe9589b2eb82394af2c41b203c99fc52e79f5bb9b849da74f41bbfd97ccf5173... | confirmed |
2022-06-23 04:55 UTC | 10,032.03 mSCP | 1a28b8326dbd1d4c2298d94eb06deffa20bc39c64917f0fce4b04453d78efc9a... | confirmed |
2022-06-22 09:40 UTC | 1,093.54 mSCP | 68e664b5673b4a2b246c5da494bc3231e4a2b5b090b2c126b182cf896683f906... | confirmed |
Show more... |
All-Time Paid Out: 61,489.94 mSCP
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.