How to use sequential UUID primary key for range query by date
The code for such is here, but it only works for "Type 1" UUIDs.  It's a matter of shuffling the bits around.  And while you are at it, BINARY(16) is more compact than VARCHAR(36) or whatever you have now.

More

By rearranging the bits of a type-1 UUID, you can take advantage of "locality of reference" when using an index on it.  For example, if you had News articles.  Users tend to look at recent articles and not touch the old ones.  New rows will be cached; old ones will drift into oblivion.

A suitably rearranged UUID would provide the equivalent of ORDER BY datetime.