Support for searching via EVM tx hash

[mgarbs]

Problem

Currently, you cannot search by tx hash

But you can find it if you construct the URL as such:
{network}/tx/0x3daf41735d1ca3d7eef4116a92cb5548a3510afab5c1d65d0f6cd19fa9ef2115

Solution

• add support to search by that tx hash

Alternatives

No response

[Nana-EC]

I'd like to propose an update to this ticket.

Hash searching capability is limited due to the scaling implications on the mirror node.
In the mean time it is possible to utilize a few API's to get to the Hedera transaction that maps to the EVM hash provided.

The mirror node explorer should add the following logic for EVM hashes, this will not be for HAPI hashes

1. Check the hash length. If it's of the matching EVM hash length and structure then call mirror node /api/v1/contracts/results/{hash}
2. If a 200 response is returned then extract the timestamp and call /api/v1/transactions?timestamp={timestamp}
3. If a 200 response is returned then extract the transactionId
4. Use the transactionId in the normal transaction details retrieval process.

If any step fails then display the normal transaction not found.

[SimiHunjan]

There is Hedera transction hash and an evm transaction hash. This issue references to search by EVM transaction hash.