Interpret a UUID
Back
Your input: 3c38ef36-5704-800d-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:3c38ef36-5704-800d-87ea-5ce32bd83b97
URI: uuid:3c38ef36-5704-800d-87ea-5ce32bd83b97
Microsoft GUID syntax: {3C38EF36-5704-800D-87EA-5CE32BD83B97}
C++ struct syntax: { 0x3c38ef36, 0x5704, 0x800d, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.80049300172319587511178387094687464343
As OID (Microsoft): 1.2.840.113556.1.8000.2554.15416.61238.22276.32781.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.4339481257638658061.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.1010364214.1459912717.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.15416.61238.22276.32781.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0x3c38ef36570400d07ea5ce32bd83b97]
Custom data block1 (32 bit): [0x3c38ef36]
Custom data block2 (16 bit): [0x5704]
Custom data block3 (12 bit): [0x00d]
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: [0x3c38] 0b0011110000111000
Milliseconds: [0xef] 936 (deviation -2ms..2ms)
Seconds: [0x36] 54
Minute of day: [0x0457] 1111 (18:30)
Day of year: [0x0d0] 208 (Day=27, Month=7)
Unused 2 bits: [0] 0b00
Year: [0x7ea] 2026
Signature: [0x5ce32bd83b97] HickelSOFT "SQL Server Sortable Custom UUID", Version 3 (very likely)
UTC Date Time: 2026-07-27 18:30:54'936 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing