Interpret a UUID
Back
Your input: 4a647a2e-f100-830a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:4a647a2e-f100-830a-87ea-5ce32bd83b97
URI: uuid:4a647a2e-f100-830a-87ea-5ce32bd83b97
Microsoft GUID syntax: {4A647A2E-F100-830A-87EA-5CE32BD83B97}
C++ struct syntax: { 0x4a647a2e, 0xf100, 0x830a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.98884579546990884708900623655070350231
As OID (Microsoft): 1.2.840.113556.1.8000.2554.19044.31278.61696.33546.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.5360543798508159754.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1248098862.4043342602.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.19044.31278.61696.33546.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x4a647a2ef10030a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x4a647a2e]
Custom data block2 (16 bit): [0xf100]
Custom data block3 (12 bit): [0x30a]
Custom data block4 (14 bit): [0x07ea]
Custom data block5 (48 bit): [0x5ce32bd83b97]
Interpretation of HickelSOFT "SQL Server Sortable Custom UUID", Version 3
Random 16 bits: [0x4a64] 0b0100101001100100
Milliseconds: [0x7a] 478 (deviation -2ms..2ms)
Seconds: [0x2e] 46
Minute of day: [0x00f1] 241 (04:00)
Day of year: [0x0a3] 163 (Day=12, Month=6)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-06-12 04:00:46'478 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing