Swim Docs
  • Introduction
  • 📖Tutorial
    • Swap
      • Solana <> Solana
      • Solana -> BNB/ETH
      • BNB/ETH -> Solana
      • BNB/ETH <-> BNB/ETH
    • Add/Remove Liquidity
    • FAQ
    • Metapool
    • Polkadot and Kusama Ecosystem
      • Karura Guide
      • Acala Guide
  • ⚙️Troubleshoot
    • Diagnosing Failed Swap Transactions
      • Solana -> BNB/ETH
      • BNB <-> ETH
      • BNB/ETH -> Solana
      • Metapool Transactions
    • Wormhole
      • Wormhole-wrapped Tokens
      • Unconfirmed Wormhole Transactions
    • Common error messages
  • Swim Protocol
    • Roadmap
    • Swim Team
    • Audits
    • Contracts
    • Investors
  • Tokenomics
    • SWIM Token
  • Links
    • Community & Contacts
    • Whitepaper
Powered by GitBook
On this page
  1. Troubleshoot
  2. Diagnosing Failed Swap Transactions

Solana -> BNB/ETH

Reading this section will help you understand where the transaction failed and better diagnose the problem

PreviousDiagnosing Failed Swap TransactionsNextBNB <-> ETH

Last updated 3 years ago

This is a typical set of transactions you would see on a blockchain explorer if you are swapping starting from Solana.

Transaction "3bPEh6..." involves swapping the asset, so in this case you are swapping from USDC SPL into Wormhole-wrapped BUSD. If your swap failed and you only see the transaction where your native token is converted to a Wormhole-wrapped token, please refer to “” to resolve the problem.

Transaction "3unL2p..." is the Wormhole-wrapped BUSD entering the bridge. If the bridge interaction is successful, you will see a corresponding transaction on the destination chain explorer showing that you have received the native token. In this example, it is transaction "0x88f32ed". If you encounter a case where a token is entering the Wormhole bridge but there is no corresponding transaction where it is leaving the bridge, please refer to "" to resolve the problem.

⚙️
Wormhole-wrapped Tokens
Unconfirmed Wormhole Transactions
Solscan
Bscscan