It might show properly the order of custom json txs that are put into one transaction, I am not arguing about that.

However, I was talking about multiple separate transactions that are in one hive block. Look for example at https://he.dtools.dev/@pdnejoh. This bot once in a while cancel its orders and then make new ones. In separate transactions, however still in one block (most of the times). And the order of transactions are not always shown properly on your site (seems quite random).

Example:

5188974a6d00b5589c2ce3b944861d5c40b6c7b1 (newer according to your explorer as it is above the second one)
0b3ddccb88a9125b13cd5e313a6b8ae0783209b2 (older according to your explorer)

https://hiveblocks.com/tx/5188974a6d00b5589c2ce3b944861d5c40b6c7b1 (6th tx in the block 44,149,975)
https://hiveblocks.com/tx/0b3ddccb88a9125b13cd5e313a6b8ae0783209b2 (9th tx in the block 44,149,975)

The transaction that is newer according to your explorer is actually closer to the start of the Hive block, so it is executed sooner and so is "older".

It just seems weird to see this bug, not really urgent thing to fix.