My OperaThe My Opera forums have been replaced with forums.opera.com. Please head over there to discuss Opera's products and features
See the new ForumsYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
Your first post, so welcome to the Opera forums! 
There is no user-friendly way that I know of, but the global_history.dat records your browsing history (and populates the history list you can view within the browser) with a 10-digit Unix Epoch time stamp for each URL each time you visit. If you only need to know the time for one or a few URLs, It is fairly straightforward (but somewhat cumbersome) to open the global_history.dat file in a text editor, find the needed URL, and copy the 10-digit time stamp.
There are any number of online converters where you can paste the 10-digit stamp in a text box and the site will convert it to human-readable form (a good one that also provides a simple explanation of epoch time can be found here). Unix time is based on Coordinated Universal Time (UTC) so you will probably have to add or subtract the appropriate number of hours to convert the online converter result to your local time.
One caveat: The global_history.dat time stamp is updated (destructively) each time you visit a URL, so it will only retain the most recent visit. So if you visit a site and then think "Gee, I wonder what time I was here yesterday," it's already too late to recover the time stamp from global_history.dat.
From a computing standpoint, it would be a trivial matter to decode this 10-digit number to make it available in human-readable form in the Opera GUI (for example it is already used in Opera's bookmarks to track when the bookmark was created and when the URL was last visited), so I've always wondered why it isn't available in Opera (e.g., via mouse-over or right-clicking an item in the browsing history). I'm guessing it would also be a relatively easy Opera UserJS or extension project, but I'm not aware of any already existing solutions.
BTW, you will probably notice a second number on the line below the 10-digit Unix time code, either "-1" or another string of maybe 4-7 digits. The -1 is encoded in global_history.dat along with the timestamp above it when the URL is first visited. The 4-7 digit number replaces the -1 when the URL is visited a second time, and AFAICT reflects the amount of time between the current and previous visits. So -1 indicates that the timestamp on the line above was the first visit to the URL stored in that particular global_history.dat file (i.e., there was no previous visit from which to calculate the value on the "-1" line). I haven't yet figured out exactly how the 4-7 digit number is derived (it isn't simple subtraction of previous from current), but if my hypothesis is correct, it should be possible use it to derive the time of the last visit to the URL prior to the one on the line above. If anyone else knows how it is derived, I'd be interested to know.
There is no user-friendly way that I know of, but the global_history.dat records your browsing history (and populates the history list you can view within the browser) with a 10-digit Unix Epoch time stamp for each URL each time you visit. If you only need to know the time for one or a few URLs, It is fairly straightforward (but somewhat cumbersome) to open the global_history.dat file in a text editor, find the needed URL, and copy the 10-digit time stamp.
There are any number of online converters where you can paste the 10-digit stamp in a text box and the site will convert it to human-readable form (a good one that also provides a simple explanation of epoch time can be found here). Unix time is based on Coordinated Universal Time (UTC) so you will probably have to add or subtract the appropriate number of hours to convert the online converter result to your local time.
One caveat: The global_history.dat time stamp is updated (destructively) each time you visit a URL, so it will only retain the most recent visit. So if you visit a site and then think "Gee, I wonder what time I was here yesterday," it's already too late to recover the time stamp from global_history.dat.
From a computing standpoint, it would be a trivial matter to decode this 10-digit number to make it available in human-readable form in the Opera GUI (for example it is already used in Opera's bookmarks to track when the bookmark was created and when the URL was last visited), so I've always wondered why it isn't available in Opera (e.g., via mouse-over or right-clicking an item in the browsing history). I'm guessing it would also be a relatively easy Opera UserJS or extension project, but I'm not aware of any already existing solutions.
BTW, you will probably notice a second number on the line below the 10-digit Unix time code, either "-1" or another string of maybe 4-7 digits. The -1 is encoded in global_history.dat along with the timestamp above it when the URL is first visited. The 4-7 digit number replaces the -1 when the URL is visited a second time, and AFAICT reflects the amount of time between the current and previous visits. So -1 indicates that the timestamp on the line above was the first visit to the URL stored in that particular global_history.dat file (i.e., there was no previous visit from which to calculate the value on the "-1" line). I haven't yet figured out exactly how the 4-7 digit number is derived (it isn't simple subtraction of previous from current), but if my hypothesis is correct, it should be possible use it to derive the time of the last visit to the URL prior to the one on the line above. If anyone else knows how it is derived, I'd be interested to know.
Originally posted by LeoCG:
Menu > History (or ctrl+shift+H) will show the date and time of the last visit to a site.
Fantastic! That's just too good for me to even feel embarrassed! ...well, after I finished laughing, maybe a "teeny bit." I use Ctrl+H all the time to pop open the History panel, but I never knew about Ctrl+Shift+H. ...and popularity counts, too. ...Nice!
...Well, like I said, from a computing standpoint it's a trivial matter to decode, so I've always wondered why it wasn't available. I looked and never found it and never thought to ask... ...so I'm glad daenar84 did!