I did not manage to figure out what the hex number mean, but the second number is ANSI date, that is the number of days elapsed since 1st January 1601. The parameter is the number of seconds elapsed since 1900-01-01 00:00:00, but it has reverse byte order, the first byte is the least significant (1900-01-01 00:00:01 is encoded as 0x01000000). To have w32tm print out 15th January 2013 22:00 UTC, use this command:
w32tm /ntpte 0xe04fa0d4
or
w32tm /ntpte 3763314900
(conversion from hex to decimal is as if the byte order was normal).
EDIT: It seems that the hex value printed by w32tm is a 64-bit integer representing the number of 100-nanosecond intervals since 1st January 1601. From this article I know this is how Windows stores FILETIME.
EDIT2: After some more playing I found two another things:
Parameter passed to
w32tm /ntpte
is really a 64-bit integer. As I wrote before, most significant 32-bits represent the number of seconds since 1900-01-01 00:00:00, while least significant 32-bits represent the fraction of second. The whole 64-bit number represents the number of 1/(2 to the power 32) second intervals since 1st January 1900. So0x0000008000000000
is equal to 1/2 second after 1900-01-01 00:00:00.The hex value printed by
w32tm /ntpte
can be directly passed as a parameter tow32tm /ntte