Dodoswap
Dodoswap order history connects your first swap to its transaction record
Dodoswap provides an order history that helps you locate your first swap’s status and transaction hash. Use that hash to inspect the blockchain receipt, then match the tokens sent and received to the intended exchange. A completed approval or a submitted transaction alone does not establish that your swap delivered tokens to the receiving address.
Updated ·
Start with the exchange you intend to authorize: its network, assets, input amount, and expected recipient. Those details let you distinguish the intended swap from nearby wallet activity and interpret the record after submission.
In short: Match the swap’s transaction hash to its receipt and token transfers before treating an order-history entry as a completed exchange.
Choose the record that matches the order type
An ordinary swap on one network has a different completion check from a limit order or a cross-chain exchange. A limit order can remain open before execution, while a cross-chain exchange also needs a destination outcome. For a same-network swap, concentrate on the execution transaction and its resulting transfers. Keep the selected mode in view when reading history: an order’s creation time does not necessarily mark an exchange of tokens.
Preserve the starting details before confirmation
Your starting record should describe what you intend to exchange, before later balances or refreshed quotes obscure it. A brief note or screenshot can preserve the relevant details without depending on a history display retaining every quote field.
Account, network, and token identity
Record the connected account, selected network, and input and output assets. For ERC-20 tokens, record their contract addresses; identify native currency by its network and name. Token symbols help you read the entry, but the contract address distinguishes an ERC-20 token on that network. Include the intended receiving address wherever it differs from the account submitting the transaction.
A starting balance also helps explain the eventual change. Keep balances in token units rather than relying on a fiat estimate. Later transfers can change those balances, so a before-and-after comparison becomes less reliable once other activity intervenes.
The terms attached to the swap
Keep the input amount, quoted output, and minimum received amount when the interface supplies it. Slippage tolerance affects acceptable execution; the quote itself does not establish the final receipt. Review the spending permission and estimated network cost before confirming. If the transaction details do not match your intended exchange, reject the request before signing.
Where can I find my swap’s transaction hash?
Find the transaction hash in the Order History section of the trading page, alongside the corresponding swap entry. The Order History view includes an order’s status, rate, creation date, and transaction hash. Match the entry to your account and intended exchange before opening its blockchain record.
A transaction hash identifies the transaction whose receipt you need. Use the explorer for the network where you submitted it. If the application has not displayed the entry, your wallet’s activity record may provide the hash. An empty history view alone does not establish whether the transaction reached the network.
Keep approval receipts separate from swap receipts
A successful approval explains a permission change, not a completed token exchange. An ERC-20 approval sets how much a specified spender may transfer from the token owner’s account. When approval requires a separate transaction, that transaction has its own hash and receipt.
The swap receipt should correspond to the exchange action. A wallet entry showing only an approval cannot establish the output amount or recipient. If the required allowance already exists, a new approval transaction may be unnecessary. Count the actions that actually occurred rather than expecting every first-session history to contain the same entries.
What does the transaction status establish?
The receipt’s status establishes whether that transaction executed successfully; identifying the requested action and resulting transfers establishes whether it completed your swap. A successful status on the wrong transaction answers the wrong question.
Pending or missing receipt
A pending EVM transaction does not yet have an execution receipt. EVM means Ethereum Virtual Machine, the execution environment used by compatible networks. While the transaction remains pending, its hash identifies an outstanding submission rather than a completed exchange.
A missing lookup result needs a narrower check. Confirm the network and full hash before interpreting the absence. The lookup service may not know the transaction yet. Avoid submitting another exchange merely because the first entry has not appeared.
Successful or failed execution
A successful receipt allows you to examine the recorded outcome. Check that it belongs to the swap and that the intended recipient received the intended token. The transaction’s top-level destination can be a contract, so it need not equal the address receiving the output tokens.
A failed receipt means that transaction did not successfully execute the swap. Keep its hash with the failure details. A retry creates a separate attempt; retain that distinction so a later success does not obscure what happened to the original submission.
Reconcile the amounts with the receiving account
Compare the actual input and output amounts using each token’s own units. The transaction’s transfer records identify movements between addresses, while the recipient’s balance provides another check on delivery. For ERC-20 tokens, inspect transfers from the correct token contract. A matching symbol on an unrelated contract does not identify the intended asset.
Token decimals determine how raw integer amounts become readable quantities. An explorer normally performs that conversion, but raw event data may not. Comparing a raw integer with a formatted wallet balance can create an apparent discrepancy even when they describe the same amount.
The execution rate expresses received output units per spent input unit, or its inverse when the display uses the opposite direction. Confirm that direction before comparing it with the quote. Keep network costs separate from token output: when the native currency also funds the input, its balance decrease can include both the swap amount and execution charges.
A short check before closing the first swap
For a same-network swap you intend to make, use the selected account and token pair as the starting record. Check that the interface offers a route for your selected network, pair, and amount. Before signing, check the account, asset identities, recipient, minimum received amount when supplied, and available balance for the input and network costs. If the route requires an ERC-20 allowance, check that the intended spender has enough permission for the input amount and complete any required approval first. Then confirm the intended swap once and follow its transaction hash through history.
- If the account, network, asset identities, or recipient differ from your intended exchange, stop before signing.
- If the swap requires an allowance that is missing or too small, approve the intended spender for the required amount and distinguish any approval transaction receipt from the swap.
- If the submitted swap remains pending, continue tracking that hash without creating another exchange.
- If execution succeeds, match the output asset and recipient to the recorded transfer, and compare the received amount with the minimum you accepted when one was supplied.
- If execution fails or the received amount remains unexplained, retain the record and investigate before another attempt.
The first swap is accounted for when successful execution and delivery agree with the intended exchange. An unresolved status calls for further inspection, not another signature merely to refresh history.
Keep enough detail to revisit the exchange
Save the network and full transaction hash with the account, asset identities, any applicable token contract addresses, and actual amounts. Preserve the original quote separately if you want to compare expected and executed output later. A screenshot helps capture the display, while the hash lets you retrieve the underlying transaction again.
Before making another swap, decide whether the previous one is fully reconciled. If a difference remains, identify whether it concerns token identity, recipient, amount, or execution status. That specific question determines which part of the record you need next.
Questions and answers
Can I inspect a Dodoswap receipt without connecting my wallet?
You can inspect a public blockchain receipt using its transaction hash without connecting a wallet. Select the corresponding network’s explorer and look up the hash. Reading that record does not require a token approval, recovery phrase, or transaction signature.
What does a zero value field mean on my swap transaction?
A zero top-level value can mean the transaction sent no native currency with the contract call. It does not establish that no tokens changed hands. A swap involving ERC-20 tokens can record token movements in transfer events while the transaction’s native-currency value remains zero.
How should I interpret several transfers under one swap hash?
Several transfers can belong to the same routed exchange. Contracts may move assets through intermediate pools before delivering the output. Avoid adding every transfer together as though each represented another payment from your wallet. Identify the input leaving your account and the intended output reaching its recipient.
Does removing a token allowance erase the completed swap?
Removing an allowance changes the spender’s remaining permission and does not erase a completed swap record. The earlier execution remains part of blockchain history. Treat a later allowance change as separate activity when reviewing the wallet’s transactions.
Is a missing fiat valuation evidence that my swap failed?
A missing fiat valuation does not establish a failed swap. Fiat displays need price data in addition to token balances. Check the execution status and actual token amount before interpreting the valuation field; a received token can have a balance even when the interface lacks its price.
Will swapping the received tokens back undo the original order?
Swapping back creates a new exchange rather than undoing the original order. The new transaction has its own execution conditions and costs, and it may return a different amount. Both completed exchanges remain separate records, so reversing the direction does not remove the first swap from history.