Searching for a transaction that's been submitted, but has not yet propagated to the explorer's node

[rhyslbw]

When clicking a transaction link that was just created in a wallet application, the explorer will likely present a 404. This is expected as two nodes are only eventually consistent, however the UX could be improved to handle this scenario as a loading state. Encoding the URL with a retry param would allow applications implementing links to improve their user experience, and ensure we're only changing the logic to match this specific flow. A timeout of reasonable length should also be implemented.