Detect the version and variant of a UUID and recover the creation time from v1, v6 and v7, with a MAC-address check and notation normalization
Braces {...}, a urn:uuid: prefix, uppercase letters and the 32-digit hyphen-less form are all treated as the same UUID.
A UUID is 32 hex digits written as 8-4-4-4-12. The first character of the third group is the version and the first character of the fourth group is the variant. A variant of 8, 9, a or b means a standard UUID (RFC 4122, superseded by RFC 9562). Anything else is a legacy scheme or the old Microsoft form.
v1, v6 and v7 carry time. In v7 the first 48 bits are milliseconds since the Unix epoch, so reading the leading 12 hex digits as a number gives the date directly. v1 and v6 count 100-nanosecond units from 15 October 1582; to reach Unix time, divide by 10000 and subtract 12219292800000 milliseconds. v4 is random, and v3 and v5 are hashes of a name, so neither yields a time.
The last 12 digits of v1 and v6 are the node field, originally the MAC address of the generating machine. Because that identifies the machine, many implementations fill it with random bits instead. The tell is the lowest bit of the first byte, the multicast bit: if it is 1, the value is random. This tool reads that bit and says whether the node could be a real MAC address.
The first character of the third hyphen-separated group is the version digit. In 017f22e2-79b0-7cc3-98c4-dc0c0c07398f that group starts with 7, so it is a UUID v7. This tool normalizes the notation first, then reads that digit.
Yes. In v7 the first 48 bits (12 hex digits) are milliseconds since the Unix epoch, so you simply read that part as a number. v1 and v6 also carry a timestamp, but in 100-nanosecond units counted from 15 October 1582, so a conversion is needed. v4 is purely random and carries no time.
No. Detection and time conversion run entirely in your browser, and the UUID is never sent to a server.