I built a new thing if you’re a dev building in crypto/web3 that’s a little tools that’s hopefully very helpful. 
txha.sh 

Read more for the use case 👇🏻

Engineer @ Syndicate, prev: Rainbow, Foundation & Cloudflare /poetic-web, builds caststorage.com

Or you’ve hard coded a block explorers url into a “view tx” link in your UI only to find that you’ve deployed it and now users are wondering why tx’s aren’t showing.

Txha.sh is created to solve that problem quickly and easily simply pass a txhash to the txha.sh domain and the system will scan for its existence across all chains that are supported and redirect immediately once found. It’s then cached for immediate redirecting in the future.

Currently we support 
Ethereum (mainnet/sepolia)
Base (mainnet/sepolia)
OP (mainnet/sepolia)
Zora (mainnet/sepolia)
Arbitrum One (mainnet/sepolia)
Polygon (mainnet/amoy)
World Chain (mainnet/sepolia)

If you want one added just DM me. ✌🏻

If you’re building multi chain apps on testnet and mainnet environments you’ve probably ran into the issue where you’ve posted a tx hash into the wrong block explorer only to sit there and wonder why it’s never appearing.

Very nice. Brutalist web aesthetic is in 👌

/blockhead・open-source interface for web3・explore EVM networks, accounts, smart contracts, blocks/txs, tokens/DeFi/NFTs, IPFS, ENS, Farcaster and more

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

Go for it. Which endpoint? There is only one so far but you can use it if you need it

FYI if you want to trigger a workflow you’ll need to hit the main url txha.sh/0x… then you can use the status one to find the result

Super neat. Would you mind if I used this as an API for resolving transaction hashes in @blockhead?

Whichever one the hash turns up on. As the chance of a repeated hash is near impossible

Really cool, but how do you determine which explorer gets preference?

@superxi this could be interesting for us.