Explorer search returns a different address than the exact gateway address entered

Nobody has claimed this yet.

## Summary

When searching for a specific gateway address in the Livepeer Explorer search modal, the search result shows a different address instead of the exact address entered.

## Address searched

`0x8a8053c21696f27ed305a03bd1efc5d068d91d0e`

This address is intended to be a gateway address.

## Actual result

The search modal returns a different address:

`0x87861c...f70478`

Selecting the result appears to navigate to that different address rather than the gateway address that was entered.

## Expected result

When an exact address is entered into Explorer search, the matching address should be returned, or the UI should clearly indicate that there is no exact match.

It should not show a different address as if it were the intended result.

## Steps to reproduce

1. Open Livepeer Explorer.
2. Click the search icon in the top navigation.
3. Enter the address:

`0x8a8053c21696f27ed305a03bd1efc5d068d91d0e`

4. Observe the search result shown in the modal.

## Evidence

Reporter-provided screenshots show:

1. The searched address entered in the Explorer search modal.
2. The Explorer UI after the search result/navigation, where a different address appears to be surfaced.

## Notes

I am not sure whether this is an indexing issue, fuzzy-search issue, address normalization issue, or gateway/orchestrator lookup issue. The report is only that the visible search behavior returned a different address than the exact address entered.

Reproduce the issue in the Livepeer Explorer search modal using the address provided and observe the returned result and navigation. Trace the search flow from the modal to determine why an exact address yields a different address; done means the exact matching address is returned, or the UI clearly reports that no exact match exists.

Written by the indexing model from the issue text.