Investigate a failed lookup without creating another payment
- Return to the sending history
Copy the full reference and any original explorer link. Keep the network and the exchange instruction in the same support note. If a spreadsheet shortened a long value or removed a fractional timestamp, use the original wallet record to resolve the missing detail.
- Use the documented lookup format
The Mirror Node REST documentation provides a transaction-details lookup by transaction ID. A particular explorer can expose a different search interface. Follow that interface’s requirements rather than moving a consensus time into the ID simply because both values look like timestamps.
- Read the resulting record
Once found, review its result and the HBAR transfer details against the required destination and amount. The fee payer is part of the standard ID, but the ID alone is not a complete list of the transfer’s participants. Establish the actual payment before discussing the Bitcoin payout.
The timestamp inside an ID has a specific job
Hedera identifies a standard transaction using the fee payer’s account and the transaction’s valid-start time. Its consensus timestamp describes a different event. A history screen can display both without implying that either field is a typing error. Copy the actual transaction reference before interpreting a difference between the displayed times.
Suppose a fictional wallet export has a column called submitted time and a separate column called consensus time. Neither column heading tells you that its value can replace the timestamp embedded in the transaction ID. An export prepared for a bookkeeper can omit details that an explorer lookup needs. Request the original reference from the sender rather than manufacturing one.
Match each field to the question you are asking
| Field or record | Useful question | Unsafe substitution |
|---|---|---|
| Original standard transaction ID | Which transaction did the sender identify? | Replacing its time with consensus time |
| Valid-start time | Which starting reference forms part of the ID? | Treating it as the final receipt time |
| Consensus timestamp | When was the transaction ordered by consensus? | Combining it with an arbitrary account to invent an ID |
| Result and transfer details | What actually happened to the intended HBAR payment? | Assuming a successful search proves the required payment |
Send a record that another person can verify
A useful message includes the unchanged transaction reference, the network, the intended payment details and the exact search error or unexpected result. If you supply both timestamps, label them. This helps the recipient distinguish an unsuccessful search from an unsuccessful transfer without asking you to send HBAR again.
Hedera’s REST reference notes that submissions to multiple nodes can produce separate successful and duplicate records sharing one transaction ID. If several rows appear, inspect their results instead of counting every row as another payment. Keep the actual exchange funding separate from a screenshot of an unrelated operation or a list of search matches.
Hedera lookup questions
- Is the timestamp in a standard transaction ID its consensus time?
- No. Hedera forms the standard ID from the fee payer and valid-start time. Preserve the original ID.
- Should I resend HBAR if one explorer search fails?
- A failed search does not establish payment failure. Resolve the original transaction and lookup format first.
- Does a found ID alone prove the exchange received the intended payment?
- No. Check the result and transfer details against the current funding instruction.
- Do several records with one ID always mean several successful payments?
- No. The documented response can include duplicate submissions. Read their results.
Primary Hedera documentation
- Hedera transaction IDs and consensus timestamps
- Hedera Mirror Node: transaction lookup and duplicate records
Reviewed: