THE QUICK ANSWER
Select the network recorded by the sender, then enter the complete public transaction hash or signature. A matching format does not prove the transaction exists or belongs to that network.
01
Use the network in the sending record
Choose Ethereum mainnet, Bitcoin mainnet, TRON mainnet or Solana mainnet. Copy that choice from the sending service’s transaction record rather than guessing it from a token name or a hash’s appearance.
Only these four mainnets are supported. Testnets, Base, Polygon and other chains are outside this selector. Several networks can use similar-looking identifiers, so a valid-looking hash does not identify the network by itself.
Keep preparation separate from lookup
Sender record
Read the network and complete public transaction identifier.
Local format check
The form prepares a fixed mainnet explorer link.
Reader opens explorer
The external site can then retrieve its own transaction record.
Original workflow showing when the public identifier reaches an external explorer.
Original explanation · not an account screenshotTry it with your own details.
This tool keeps your input in this page. It does not upload it, add it to the address or save it. Downloads happen only when you choose them. Reset the form when you finish.
02
Paste the public transaction identifier
For Ethereum the form requires 0x followed by 64 hexadecimal characters. Bitcoin and TRON require 64 hexadecimal characters without that prefix. Solana requires a complete Base58 transaction signature that decodes to 64 bytes; an account address is a different input.
Copy the transaction identifier itself, not a full explorer URL, payout reference, wallet address or screenshot. No private key, recovery phrase, wallet connection or sign-in is needed. If the sending service has only a request number, ask whether it has created a public transaction record.
| Ethereum mainnet | etherscan.io/tx/ plus the entered hash |
|---|---|
| Bitcoin mainnet | blockstream.info/tx/ plus the entered hash |
| TRON mainnet | tronscan.org/#/transaction/ plus the entered hash |
| Solana mainnet | solscan.io/tx/ plus the entered signature |
03
Understand what the format check establishes
Prepare the link to see whether the identifier fits the selected network’s supported format. The tool does not fetch a transaction, query an API, check confirmations or decide whether a receiving service has credited an account.
The result gives an external link only after the format check succeeds. Opening that link sends the public identifier to the chosen explorer. Confirm the network first; preparing the link on this page does not make that external request.
A link is not a confirmed payment
Format fits
The identifier passed this form’s structural check.
Explorer has a record
Read that explorer’s actual transaction result and details.
Receiving service credit
Check the receiving service’s separate account record.
These are separate observations; the form makes only the first check.
Original explanation · not an account screenshot04
Read the record on the explorer itself
Etherscan and Solscan document transaction identity and result fields. On the explorer, compare the actual transaction, result and relevant sender, recipient and asset information with your sending record. Do not substitute the form’s format-success message for those external facts.
If an explorer cannot find the identifier, keep the original network and sender reference together for support. This tool cannot diagnose why the record is absent or turn a blockchain result into a partner-crediting promise. It does not save or upload the form input; use Reset this form when finished.
BEFORE YOU CONTINUE
Quick checklist
- Select the exact supported mainnet from the sender’s record.
- Paste the complete public transaction hash or signature.
- Treat a format match as a format match.
- Open the prepared external link only after checking the network.
- Compare the explorer’s real record with the sender’s details.
Official sources
Tool behaviour was checked against StrikePot’s form and browser implementation on 26 October 2026 (America/Toronto). The external references below explain the relevant formats and source records.
- Etherscan — What is a Transaction Hash? · reviewed
- Solscan — Transaction Details · reviewed
- Blockstream — Bitcoin mainnet explorer · reviewed
- TRONSCAN — Official explorer · reviewed
Implementation inspected: explorer form, gtExplorer and result-link handler. The four URL patterns and exact identifier checks are code-defined; no external transaction or status is fetched. Etherscan and Solscan documentation were directly readable. Blockstream returned a JavaScript shell and TRONSCAN returned HTTP 403 during extraction; no unobserved explorer UI or transaction was invented. No API key, wallet connection, transfer or live hash lookup was used.
