localhost / 18081
Height: 1457340/1457341 (99.9%) on mainnet, smart mining at 0 H/s, net hash 299.95 MH/s, v6, up to date, 8(out)+0(in) connections, uptime 0d 0h 22m 22s
Height: 1457340/1457341 (99.9%) on mainnet, smart mining at 0 H/s, net hash 299.95 MH/s, v6, up to date, 8(out)+0(in) connections, uptime 0d 0h 22m 30s
Height: 1457346/1457346 (100.0%) on mainnet, smart mining at 0 H/s, net hash 303.50 MH/s, v6, up to date, 9(out)+0(in) connections, uptime 0d 0h 30m 51s
Height: 1457346/1457346 (100.0%) on mainnet, smart mining at 0 H/s, net hash 303.50 MH/s, v6, up to date, 9(out)+0(in) connections, uptime 0d 0h 30m 53s
Height: 1457346/1457346 (100.0%) on mainnet, smart mining at 0 H/s, net hash 303.50 MH/s, v6, up to date, 8(out)+0(in) connections, uptime 0d 0h 31m 32s
Height: 1457346/1457346 (100.0%) on mainnet, smart mining at 0 H/s, net hash 303.50 MH/s, v6, up to date, 8(out)+0(in) connections, uptime 0d 0h 31m 33s
Height: 1457524/1457524 (100.0%) on mainnet, smart mining at 0 H/s, net hash 298.84 MH/s, v6, up to date, 8(out)+0(in) connections, uptime 0d 6h 16m 40s
Whats your question?
Embedded Monero version: v0.11.1.0-2-gc328163
GUI version: v0.11.1.0
And what is the problem? Is it the sudden time difference between the last two entries?
Please always describe the issue clearly, it helps to speed up the fix when the developer can get all the needed information from the first defect report.
Sorry, its just because I am starting up. I was wondering if I have to use another address in the deamon section, to get it work. Also I have been mining very long time and no monero?
Thougt I had a bad setup....
But if the stats looks ok, then I will cary on,.
Where can I seek understanding about:
Height mainnet, net hash up to date connections uptime
There are some steps in this guide on how to verify your blockchain status:
Your output looks OK to me fwiw.
+resolved