Interpret a UUID
Back
Your input: dfdcea2a-2203-8f0a-87ea-5ce32bd83b97
Various notations:
URN: urn:uuid:dfdcea2a-2203-8f0a-87ea-5ce32bd83b97
URI: uuid:dfdcea2a-2203-8f0a-87ea-5ce32bd83b97
Microsoft GUID syntax: {DFDCEA2A-2203-8F0A-87EA-5CE32BD83B97}
C++ struct syntax: { 0xdfdcea2a, 0x2203, 0x8f0a, { 0x87, 0xea, 0x5c, 0xe3, 0x2b, 0xd8, 0x3b, 0x97 } }
As OID (ISO/ITU-T 128 bits): 2.25.297564897790870774429859876011553340311
As OID (Microsoft): 1.2.840.113556.1.8000.2554.57308.59946.8707.36618.34794.6087467.14171031
As OID (Waterjuice 2x64 bits): 1.3.6.1.4.1.54392.1.16131025432014458634.9793742470433487767
As OID (Waterjuice 4x32 bits): 1.3.6.1.4.1.54392.2.3755797034.570658570.2280283363.735591319
As OID (Waterjuice 8x16 bits): 1.3.6.1.4.1.54392.3.57308.59946.8707.36618.34794.23779.11224.15255
Interpretation of the UUID:
Variant: [0b10_] RFC 9562 (Davis-Peabody-Leach)
Version: [0x8] Custom implementation
Custom data: [0xdfdcea2a2203f0a07ea5ce32bd83b97]
Custom data block1 (32 bit): [0xdfdcea2a]
Custom data block2 (16 bit): [0x2203]
Custom data block3 (12 bit): [0xf0a]
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: [0xdfdc] 0b1101111111011100
Milliseconds: [0xea] 917 (deviation -2ms..2ms)
Seconds: [0x2a] 42
Minute of day: [0x0322] 802 (13:21)
Day of year: [0x0af] 175 (Day=24, 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-24 13:21:42'917 (deviation -2ms..2ms)
Lookup this UUID at MagnumDB, Google, Bing