One thing is that your log contains "time" as time prefix and "time: " as the string really preceeding the actual timestamp. You could be more precise about that in case you have the word "time" somewhere within the event - you don't want splunk to have more work trying to guess where your timestamp is - the more precise you are, the better and more efficiently splunk works.
Another thing is that you don't have your timeformat defined. Don't leave splunk guessing whether something is a timestamp or not. It's best to have both TIME_PREFIX defined as precisely as possible and TIME_FORMAT set to the timestamp format you're expecting. It makes a huge difference on the input performance.
Next, you don't have MAX_TIMESTAMP_LOOKAHEAD set so it's probably at default 128 characters. Your events seem relatively long and the timestamp isn't placed at the beginning of the event so you might run into trouble if your "data part" of any particular event gets too long and timestamp gets pushed further down the event.
And finally - the timestamps look pretty much OK in terms of the value but shifted in timezones. There can be several reasons - the timezone from the timestamp could have been misinterpreted or you can have wrongly set timezone on your end (in the GUI). Remember that if you're located in a different timezone than reported in the event, the timestamp will get rendered by the GUI according to your timezone. Your events (at least one of them) is supposed to be in Zulu time (GMT). So if you're in another timezone, splunk's GUI may show it as a different hour.
