If your swap is pending, the deposit may still be waiting for a place in a block or for enough confirmations after it was included. Congestion can stretch either wait, so first check the transaction on its source blockchain before deciding what to do.
What “deposit observed” means
A deposit is observed when the swap protocol detects the transaction on the blockchain it came from. That is different from your wallet showing “sent”: a wallet can broadcast a transaction before any block includes it. For Bitcoin, the unconfirmed transaction sits in the mempool, where it competes with other transactions for limited block space.
After a miner includes it in a block, the transaction has one confirmation. Each later block adds another. A protocol may wait for a set number of confirmations before treating a deposit as final; this helps reduce the risk of acting on a transaction that is later reversed by a chain reorganization.
For Chainflip, validators watch relevant blockchain activity, wait for the protocol’s confirmation requirement, then report the deposit to its State Chain. That observation and reporting stage follows the source-chain activity. JIT AMM processing comes after the deposit is accepted, so a delay before observation is not evidence that the swap has reached pricing or execution.
Why congestion changes the wait
Congestion mainly affects the time before a transaction gets its first confirmation. When demand for block space rises, miners generally prioritize transactions with higher fee rates, measured in satoshis per virtual byte (sat/vB). A transaction offering less than the going rate can remain unconfirmed through several blocks, even though it has reached the network.
Once a Bitcoin transaction is included, later confirmations usually arrive at the pace of new blocks, which average about ten minutes apart over time. That is not a timer: individual blocks may come sooner or much later. A protocol requiring several confirmations therefore adds more variable waiting after inclusion, while the fee rate mostly affects the queue before inclusion.
For example, suppose a Bitcoin deposit is included after 40 minutes and the protocol requires three confirmations. The first confirmation arrives with that block; two more blocks are needed. At roughly ten minutes per block, the remaining wait might be about 20 minutes, but actual block timing can make it shorter or longer. These figures are illustrative, not a prediction for a particular deposit.
How to tell what is holding up a pending swap
Use the transaction ID (TXID) in a source-chain explorer and check two things: whether the transaction is visible, and whether it has a block confirmation. If it is visible but unconfirmed, the bottleneck is likely the source-chain queue. If it has confirmations, compare that count with the protocol’s required threshold; the protocol may still be waiting to accept and report it.
If the TXID is not visible, confirm that your wallet actually broadcast the transaction and that you copied the correct TXID. A transaction can also disappear from some nodes’ mempools if it waits too long or is replaced. Ask the sending wallet or service for its status before sending again; a second payment could create a separate deposit rather than speed up the first one.
chainflip.org is a service for making native-asset swaps across blockchains. Chainflip uses source-chain observation as part of that process, so a pending deposit can reflect confirmation time rather than a problem with the swap itself.
What to do if it stays pending or fails
If the transaction is unconfirmed, check whether your wallet supports fee replacement, such as Replace-by-Fee (RBF) on Bitcoin, and follow that wallet’s instructions if you choose to raise the fee. The replacement uses the same inputs and should have a higher fee rate; don’t make a new payment to the deposit address as a substitute unless the service’s instructions specifically tell you to.
If the explorer shows the required confirmations but the deposit remains pending, keep the TXID and note the confirmation count and latest block. Use the service’s normal help channel with those details. If the transaction is marked failed, check whether it was confirmed, replaced, or returned before taking another action.
Chainflip Solana swaps can help you learn more about Chainflip when comparing cross-chain options. For any pending deposit, the practical first step is to check the TXID on its source chain; that tells you whether you are waiting for block inclusion or for the protocol to finish observing confirmations.