Wrong method signature#210

We have identified an issue on blastexplorer.io where the method name is not displayed correctly when viewing the list of transactions for a contract. You can, for instance, see it here:
https://blastexplorer.io/address/0x7d6fF82345B10Aa00b50cd1b34D17854336e82E0

It indicates that for the TX 0xb68c776b92897692a455e0827a4d41f8f24dd398f3a34b27042a9d244a770541, the method displayed is ‘Adfepixw.’ However, when you enter the TX:

https://blastexplorer.io/tx/0xb68c776b92897692a455e0827a4d41f8f24dd398f3a34b27042a9d244a770541

The correct function name mintEfficientN2M_001Z5BWH() is visible in the input data field.

It seems it is taking the TX signature from the https://www.4byte.directory/ rather than the verified contract itself, which can fail to fetch the proper one when it collides like in this case.
IMHO it should first take the signature from the verified contract if it is verified, and then, if not, from the 4byte.directory