Your wallet already sent the coins, but the crypto swap deposit is still waiting for confirmations. Do not call the order stuck, and do not invent how many confirmations a YBEX deposit needs. Open the live order, read required versus seen, paste the deposit TxID into the send-side explorer, then wait remaining times that chain’s typical block time. You will know when to keep waiting and when to open official support once with Order ID plus that deposit TxID.
Summary: A confirmation is a new block stacked on your send, not a YBEX timer. Read required versus seen on this order, then check the deposit TxID on the send-side explorer. Wait while the count is still below the order threshold. Open official support once only after that count is met and the order still does not credit.
YBEX is an instant crypto exchange. Homepage copy can say exchanges are instant. Treat that as marketing. The public handling window in the Terms of Use (clause 6.5) is 30 minutes to 72 hours, not one blockchain block. Confirmations are new blocks piled on after your send. A TxID is the tracking number. The mempool is the waiting room of unconfirmed transfers. The Request Number is the unique ID. Do not create a second order for the same coins.
How to read seen vs required on the live YBEX order
Do open the current order first. Use the exchange page or Exchange History and copy the Request Number. Press F5 if the screen looks stale. Executed means funds already left for the recipient you specified. Do not name the swap stuck until you have required versus seen.
A confirmation starts when a miner includes your send in a block. YBEX help dated 27 February 2025 says at least 2 Bitcoin network confirmations before a Bitcoin exchange is processed, and names 6 as a common finality figure. That help is Bitcoin-only. A live BTC to USDT TRC-20 quote on 19 September 2026 returned minConfirmationsToTrade 1. Do not copy 2, 6, or another desk’s table onto this ticket. Required (minConfirmationsToTrade) is the minimum blocks this order needs before it can use your deposit. Seen is how many it already has. Incoming funds detected means the send was spotted. Deposit registered means the required count arrived and the deposit was credited. Do not mix minConfirmationsToWithdraw (payout-side depth) into this wait. After Executed, use the payout explorer checklist.
Workflow:
Open the live YBEX order → read required vs seen → send-side explorer on the deposit TxID → remaining × block time → wait if below the threshold → official support once if the threshold is met and still uncredited
- Open the current YBEX order and save the Request Number.
- Read required versus seen, or minConfirmationsToTrade for this quote if the page has no chip.
- Copy the deposit TxID and open the send-network explorer. Match To-address plus amount to this order.
- Read explorer confirmations: 0 means mempool, 1+ means already in a block.
- If seen is below required, wait remaining times that chain’s typical block time and refresh with F5.
- If explorer is at or above required and credit is missing, send one official packet: Request Number, deposit TxID, network, explorer URL. If Bitcoin confirmations arrived after auto-cancel, open website chat with the application number plus TxHash. Do not invent a minute limit.
How to open the send-side explorer for the deposit TxID
Do paste the deposit hash into the explorer for the network printed on the order. Bitcoin: mempool.space. Ethereum and ERC-20: etherscan.io. TRON and TRC-20: tronscan.org. Match To-address and amount to the live YBEX deposit. Don’t open the receive-side chain while you wait for deposit credit.
| What you see | What it means | Do now |
|---|---|---|
| No TxID | Wallet has not broadcast. | Confirm the send. Do not open support about confirmations. |
| 0 conf / mempool, To matches YBEX | Still in the waiting room. | Wait for the first block. Pending ETH low gas: speed-up guide. No second send. |
| 1+ conf, still below required | Deposit is real. Threshold not met. | Wait remaining × that chain’s block time. Refresh with F5. |
| Explorer at or above required, order pending | Chain met the threshold. Order has not credited. | Refresh, then official support once with Order ID plus deposit TxID. |
| Deposit registered, not Executed | Deposit credited. Swap, payout, or compliance still running. | Stop this wait. Use the stuck-order status checklist, not another send. |
Verdict: The send-side explorer is the receipt book for this deposit. Explorer “confirmed” at 1 block is not YBEX credit. Credit follows minConfirmationsToTrade on this order.
How to convert remaining confirmations into expected wait
Do compute remaining as required minus seen when seen is lower, then multiply by a typical block time for that chain. This is a rough wait, not a YBEX clock. Bitcoin averages about 10 minutes per block on bitcoin.org, with no promised min or max; a low fee can delay the first confirmation. Ethereum slots are 12 seconds. TRON produces a new block every 3 seconds. Monero targets about 2 minutes. Solana mainnet slot time moved to 300 ms on 25 August 2026.
Live quotes on 19 September 2026 show why a bigger number is not always a longer wait. ETH to BTC asked for 12 trade confirmations, about 2.4 minutes if slots are full. BTC to USDT TRC-20 asked for 1, about 10 minutes typical. XMR asked for 40, about 80 minutes. SOL asked for 200, about 1 minute at 300 ms. Don’t freeze those rows. Read this order.
How to separate 0-conf mempool delay from a count still below the threshold
Zero confirmations means the send is still in the mempool. Wait for inclusion. Do not open support at 0 confirmations. If the pending send is Ethereum with a low gas bid, follow the pending ETH speed-up checklist. Do not Cancel a deposit you still want credited.
One plus confirmations means a block already includes the send. The swap can still wait if seen is below required. Refresh the order. Keep the same TxID. Don’t treat an explorer “confirmed” badge after the first block as YBEX credit. Check how many confirmations before a crypto swap deposit is credited on this order. If Bitcoin required confirmations arrive after auto-cancel, contact website chat immediately with the application number plus TxHash. See the late Bitcoin confirmation FAQ. The public help does not state that limit in minutes. Do not invent one. Do not panic-resend.
When to open official support once with Order ID plus deposit TxID
Do wait while remaining is above zero. After the send-side explorer shows a count at or above required, refresh the tracker. If the deposit is still not registered, open official support once. Use the YBEX support page, [email protected], or website chat. Include Request Number, deposit TxID, send network, amount, and the explorer URL. [email protected] is not order support.
After deposit registered, confirmation-wait is over. Terms 2.6 say delays can be technical or compliance-related. Terms 2.7 say AML and KYC checks are mandatory for certain transactions. Clause 6.5 still allows 30 minutes to 72 hours to process the exchange. If status then sits in a hold, use the stuck swap order-status checklist. Don’t send a second deposit to “unlock” credit.
How to avoid a second deposit, fake DMs, and invented confirmation numbers
Do keep the original TxID. A second send is a second payment. Don’t paste an old deposit address. Don’t copy Kraken’s 4, Gemini’s 3, bitcoin.org’s 6, or the February 2025 “at least 2 Bitcoin” line as a universal YBEX rule. Read this order. Don’t share a seed or private key. Official Telegram is t.me/ybex_io. Anyone who DMs first and asks you to pay again is not support. When this order is finished, open a fresh ticket on the YBEX exchange widget and copy the new deposit address only.
- Save Request Number, deposit TxID, network, and explorer URL in one note.
- If remaining is above zero, wait and refresh. Do not open support at 0 confirmations.
- If the explorer already meets required and credit is missing, send one official packet.
- If the deposit is already registered, follow order status or payout steps.
- For the next swap, copy a new deposit address from a new widget order.
Frequently asked questions
How many Bitcoin confirmations does a YBEX swap deposit need?
Read minConfirmationsToTrade on this order. Help from February 2025 says at least 2 Bitcoin confirmations. A live BTC to USDT TRC-20 quote on 19 September 2026 showed 1. Do not use 6 unless 6 is on your order.
Why do Ethereum confirmations finish faster than Bitcoin?
Ethereum slots are 12 seconds. Bitcoin targets about 10 minutes per block. A live ETH quote needed 12 trade confirmations (~2 to 3 minutes if slots are full) versus 1 Bitcoin confirmation (~10 minutes typical). Multiply this order’s number by that chain’s time.
Should I open support at 0 confirmations?
No. Zero means the send is still in the mempool. Wait for inclusion. For pending ETH with low gas, use the speed-up guide. Open support after the required count is on the send-side explorer and the order still does not credit.
The explorer says confirmed, but YBEX does not. What should I do?
Explorers often mark 1 block as confirmed. YBEX credits at minConfirmationsToTrade. If that number is already met, send one official ticket with Order ID plus deposit TxID. If not, wait the remaining blocks.
Can I send a second deposit while waiting?
No. A second send is a second payment. Keep the same TxID. If the application cancelled before confirmations arrived, contact website chat with the original hash.
Disclaimer: The material in this article is not financial or investment advice. Everything stated here reflects the author's personal view and should not be treated as a recommendation to trade or invest. We make no warranties regarding the accuracy, reliability or completeness of the information presented. Cryptocurrency markets are highly volatile and can move unpredictably. Before committing any funds, every investor, trader or crypto user should study several independent sources and check the regulations that apply in their own jurisdiction.