Camelot exchange swaps connect transaction records to wallet balance changes

Quote Details Establish the Expected Balance Change

A swap quote establishes the intended input and estimated output, while the executed transaction establishes what moved. Preserve both records when checking a discrepancy. Camelot's swap parameters include the rate, price impact and minimum received. Those figures describe different aspects of execution; none replaces the resulting token balance.

Record the selected token contracts and input amount before authorizing the exchange. The minimum received defines an execution constraint, whereas the estimated output supplies a comparison point. After execution, reconcile against the actual debit and credit. An earlier quote alone cannot establish that tokens are missing.

Matching Accounts and Blocks Makes Balances Comparable

A meaningful balance comparison uses the same account and network, with an identifiable observation point on either side of the swap. Without that baseline, unrelated activity can look like an execution discrepancy.

Token Identity

For a token balance, record the contract address alongside its displayed symbol. The network also belongs in that record. A matching ticker doesn't establish that two entries represent the same token contract, and a balance on another network cannot explain the local swap output.

Observation Time

Block references make historical comparisons more precise than screenshots taken at unspecified times. Balance queries can target a particular block. However, block-end balances include all relevant activity through that block, so another transfer within the comparison interval changes the arithmetic.

Keep later transfers outside the swap calculation, or account for them explicitly.

Wallet Transfers Explain More Than a Success Label

A successful transaction status confirms execution without a top-level revert; the associated token movements explain its effect on the wallet. An approval transaction can also succeed, so the status alone doesn't identify a completed exchange.

A router may interact with several contracts during one swap. Adding every transfer in that transaction would count intermediate movements as wallet activity. Reconciliation instead follows transfers into and out of the relevant account, grouped by token contract. Match the final recipient with the account whose balance you're checking.

The transaction's destination can be a contract rather than the wallet receiving the output. That distinction matters when reading an explorer's top-level fields. Preserve the transaction hash as the identifier, then examine the decoded transfers and resulting balances.

Gas Changes the Balance Equation

Network fees create a separate debit that can make the gas asset's balance change differ from the amount exchanged. Use the actual transaction charge rather than the wallet's earlier fee estimate.

Tokens Tracked Separately From Gas

For an ordinary token without balance-changing mechanics, closing balance equals opening balance plus incoming transfers minus outgoing transfers. Apply that relationship separately to each token. Don't subtract gas from an unrelated token's quantity merely because both appear in the same wallet.

The Asset Paying Network Fees

When the same asset pays gas and supplies the swap input, its balance must cover both debits. If it arrives as output, the net increase can be smaller than the received amount. Include fees from separate approval transactions when the opening balance predates those approvals.

Record swap fees without subtracting them twice. If the executed amounts already incorporate a trading charge, an additional deduction would create an artificial shortfall. The fee breakdown explains the exchange economics; the actual movements explain the wallet balances.

Decimals Change the Display, Not the Token Movement

Raw token quantities and displayed quantities must use the same decimal scale before comparison. An apparent discrepancy can come entirely from comparing those different representations.

For a token that specifies its decimals, divide the raw integer amount by ten raised to that decimal count to obtain the displayed quantity. Preserve the raw value when exporting records, and apply the scale consistently to balances and transfers. Don't assume every token uses the same precision.

Wallet displays can round small quantities. Compare full precision before treating a residual as a missing transfer.

---

A Completed Swap With an Unchanged Wallet Display

This hypothetical example uses invented quantities and assumes ordinary tokens, separate gas payment and no other balance changes. The opening balances are 84.6 input tokens and 4.3 output tokens. A quote exchanges 23.6 input tokens for an estimated 18.2 output tokens, with a minimum received of 17.6.

The trader can stop before authorizing the swap. They review the contracts, spending permission and minimum output before authorizing the swap. The completed transaction then records a debit of 23.6 input tokens and a credit of 17.8 output tokens to the intended account.

The expected closing balances are 61 input tokens and 22.1 output tokens: 84.6 minus 23.6, and 4.3 plus 17.8. The received amount exceeds the selected minimum. If the onchain balances match those totals while the wallet still shows 4.3 output tokens, the discrepancy concerns the display. Repeating the swap would create another trade.

Open full-size image

If the execution record instead shows a credit to another account, that credit wouldn't reconcile this wallet, even with a successful transaction status. Stop further exchanges and investigate the recipient rather than treating the problem as delayed display. A completed swap has no ordinary undo operation; exchanging back requires another transaction under its own terms.

Why Does the Explorer Show Output That the Wallet Doesn't?

A wallet can omit a received token or show stale information even when the network records its balance. Confirm that both views use the same account, network and token contract before treating their disagreement as a display issue.

If the explorer's balance confirms receipt, refreshing the wallet or adding the correct token entry may resolve visibility. A transfer entry and a current balance answer different questions: tokens could have arrived and subsequently left. Check both when reconciling a later snapshot.

A Complete Reconciliation Sets the Boundary for Further Action

A reconciliation is complete when the executed movements explain the closing balances over the chosen interval. A spreadsheet can preserve that arithmetic; a wallet portfolio screen offers convenience but may round quantities or lag behind execution.

Keep the quote separate from the final record. Preserve the transaction identifier, recipient, token quantities and actual network charge so a later balance change doesn't overwrite the explanation. A display refresh requires no new exchange authorization.

The simple calculation changes when the interval includes additional transfers or the token changes balances through its own mechanics. Transfer charges and rebasing require token-specific treatment. An unexplained difference warrants examining those conditions before another swap adds more activity to reconcile.