Converting b64 to HEX outputs unexpected GUID

Hey there,

Really like your tool - trying to incorporate in some tests I'm doing with Postman.

Thing is, if I throw a GUID at the API, it returns me a B64 value that is decoded into something different.

For example:

`curl -d 'guid=2b88f261-bf4a-4972-90ad-845dac554a06' http://guid-convert.appspot.com/query`

Returns

```
{
"status": "success",
"int": "57867872278969410912862791724044732934",
"hex": "2b88f261-bf4a-4972-90ad-845dac554a06",
"b64": "YfKIK0q/ckmQrYRdrFVKBg=="
}
```

But heading over to http://tomeko.net/online_tools/base64.php?lang=en B64 to Hex decoder outputs something different!

It gives:

`61f2882b-4abf-7249-90ad-845dac554a06`

As the output result. Notice the pairs of digits are mixed up? I.e. 7249 instead of 4972.

Thanks for the tool

No source files are named. Reproduce the request at the documented /query endpoint, compare its b64 decoding with the reported GUID and external decoder, then trace the Python conversion path to determine the intended byte order. Done means the API's GUID, hex, and base64 representations agree consistently, with the expected ordering covered by a regression test.

Written by the indexing model from the issue text.