Two Transaction Hashes, One Nonce: Read the Replacement
A replacement can have a different hash while competing for the same position in an account’s transaction sequence. The final included request’s actual contents matter more than the label attached to the original attempt.
Establish the shared context
For ordinary account transactions, a replacement uses the same sender and account nonce on the same chain. A matching nonce number from another account or another chain is unrelated. Write the original hash and candidate replacement hash in separate rows, then compare sender, network and nonce before accepting an explorer’s association. A quote identifier, permit nonce or service order number belongs to a different context.
Compare the actual operations
A replacement may preserve the intended operation with different fee settings, or it may represent another operation intended to supersede it. Compare destination, native value and decoded call meaning rather than assuming identical behavior from a shared nonce. If the included replacement performed a different action, the original website’s description may no longer explain the outcome. Treat a cancellation-style label as a summary that still needs receipt and transaction evidence.
Determine what was included
Inspect the replacement’s block and receipt status. A pending replacement is still only a candidate, and submitting one does not guarantee it wins. A successful included replacement can consume the nonce even when it does not perform the original exchange. Its success also does not prove the original intended recipient received assets. Record the observed chain evidence and the time instead of collapsing the two requests into one unqualified success message.
Keep execution decisions with the wallet owner
This guide does not choose replacement fees, construct a cancellation or send a transaction. A confirmed action cannot be undone by later pressing a cancel control; consult current wallet documentation for the specific state. If a support report is needed, describe both public hashes and their relationship without signed payloads or recovery information. RunixCoin’s public swap execution remains unavailable, so no replacement workflow is offered or verified through its estimate form.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.