Dodo exchange
Dodo exchange lets you track your first swap in Order History
Updated
Dodo exchange shows your submitted swap in Order History, where you can check its status and transaction hash. Use that hash to match the entry with the blockchain transaction and confirm the output reached your account. A wallet confirmation may concern token approval, while a submitted swap may still await execution. For your first swap, keep the selected account, network and intended tokens consistent until you have checked the final result.
The short version: A transaction hash identifies your swap attempt; its execution status and resulting token transfers establish whether the exchange completed.
Your wallet, selected tokens and history entry must match
Before confirming the first swap, establish which account will spend the input token and which network will process the transaction. Keep enough native currency available for the network fee. Record the intended output token as well as the input amount. Before signing the swap, review the quoted output and slippage tolerance. The tolerance limits how much worse execution may be than the quote; execution outside that tolerance causes the swap to fail. Token contract addresses distinguish assets with similar names. These details give you something concrete to compare with the eventual transaction, especially when your wallet contains several accounts or displays balances across multiple networks.
Token approval grants spending permission. It does not establish that the exchange occurred. Identify the operation each wallet request authorizes before accepting it.
Order History connects the trading page to the transaction
Order History appears below the trading area and includes the order status, rate, creation date and transaction hash. Use the date to locate the relevant entry, then retain the complete hash. An entry describes an order; the associated blockchain record shows what happened during execution. The approval and swap can have separate records, so compare the operation as well as its status.
Does a transaction hash mean my swap completed?
A transaction hash identifies an attempt, while successful execution establishes that the network processed the requested operation without reverting it. A pending transaction still lacks a completed execution result. Check its status on the explorer for the network you selected. The same account address can exist on different networks, so searching the wrong explorer can produce an empty or misleading result.
An unresolved transaction is a reason to investigate before submitting another swap. A second submission can create another transaction rather than repair the first. Preserve the original hash while checking whether the wallet reports a replacement or a completed result.
The received token makes a successful status meaningful
When the swap succeeds, compare its output transfers with the intended recipient and exact token identity before using the received balance. The transaction details should correspond to the account you selected at the start. An approval can also show success, so the status alone does not identify the operation. Look for the exchange output associated with the swap transaction.
A routed swap can involve contract activity beyond the transfer visible in your wallet. Focus on the output your account actually received. For tokens without automatic balance adjustments, the balance increase should match the received amount when no other activity intervenes. If the output is the native currency used to pay gas, account for the transaction fee when comparing balances. Later transfers or token-specific balance mechanisms can change the comparison. A current balance therefore answers a different question from the amount a particular swap delivered.
A failed first swap followed by a checked retry
Consider a hypothetical first attempt with an input token, output token and amount you selected. Assume the account holds sufficient funds, the required approval has completed and the quoted output meets your chosen limit. All account conditions and outcomes in this example are hypothetical.
You submit the swap, then locate its transaction through Order History. The transaction reports a revert, with error details identifying an output below the permitted minimum. The swap has failed; a hash alone would not have revealed that outcome.
For this single atomic swap, the revert undoes its token exchanges. Network computation still costs gas. Reconcile the failed attempt separately from the earlier approval, which remains a distinct transaction.
Before retrying, obtain a fresh quote and reassess the available fee balance. Keep the existing slippage tolerance unless you deliberately accept a different execution bound. If the fresh quote is unacceptable, stop before signing another swap.
Assume the refreshed quote is acceptable and the retry succeeds. Its separate transaction record shows output reaching the intended account. You retain both hashes: one records the failed attempt and its fee, while the other identifies the completed exchange.
A missing wallet display needs a balance check
If the transaction shows the expected output but your wallet omits the token, inspect the account balance on the correct network. Some wallets require you to add a token before displaying it. Use the exact contract identity from the completed transfer when checking the asset. Changing the display does not perform another swap or move funds. Avoid repeating the exchange solely because the wallet has not shown the received token yet.
Keep execution costs separate from exchanged amounts
Reconciliation should account for the input spent, output received and network fees associated with the first attempt and any retry. An on-chain transaction that reverts still incurs a fee for the computation it consumes. A lower native-currency balance therefore does not prove the swap delivered output. Include a separate approval fee when an approval transaction preceded the trade.
Retain the network, account address and transaction hashes with your record of the received amount. The displayed rate helps describe the exchange, while the fee records explain additional expenditure. This separation also prevents a failed attempt from disappearing from your accounting merely because it produced no output.
Finish the first session before committing the output
Once you have reconciled the received amount with the execution record, accounting for fees and any other balance changes, you can decide whether to leave the output in the account or use it elsewhere. Viewing the record requires no further exchange. If the records disagree, pause the next action and resolve the specific mismatch first. Before submitting any retry, the reversible stopping point is the unsigned request. After a swap completes, exchanging back requires another trade with its own execution conditions and costs.
Things people ask about Dodo exchange
What does an empty Order History mean after I reject a wallet request?
An empty Order History does not by itself establish whether a transaction reached the network. Rejecting an unsigned request prevents that request from authorizing a transaction. An earlier accepted request may still exist, however. Check the wallet activity for the relevant account before concluding that the session produced no transaction.
Is the creation date in Order History the same as the confirmation time?
The creation date identifies the order entry and should not substitute for the transaction’s confirmation details. Submission and inclusion in a block are different events. For the execution time, inspect the block containing the transaction. Keep the displayed timezone in mind when comparing that timestamp with the trading page.
Can I inspect my first swap using only its transaction hash?
A public blockchain explorer can display transaction details without a wallet signature when you supply the hash and select the correct network. Reading that record does not require spending permission or a recovery phrase. The lookup can expose public account activity, so sharing the hash also shares a way to inspect the associated transaction.
Why might a replacement transaction have a different hash?
A replacement changes the signed transaction data, so it has its own hash. When your wallet reports a replacement, inspect the replacement’s actual operation and outcome. A replacement may attempt the original action with different fee settings or attempt cancellation. Keep its hash alongside the original instead of treating the first pending record as the final result.
Does the rate in Order History show whether my first swap made a profit?
The displayed exchange rate alone cannot establish profit. That calculation also needs an acquisition cost, a consistent valuation basis and relevant charges. Order History helps identify the exchange, but receiving the expected token only confirms the operational result. A successful swap and a profitable position describe different outcomes.