How many confirmations does a casino deposit need?
A deposit that's visible on the blockchain but still "pending" in your casino balance usually just hasn't reached the operator's confirmation threshold yet. Here's how to tell whether you're waiting normally — or whether something else went wrong.
What a confirmation actually is
A confirmation is one block added on top of the block that holds your transaction. More confirmations make the transaction harder to reverse, which is why an operator waits for several before it trusts the money enough to credit. Credit time is roughly block time × required confirmations, plus the operator's own processing. A block explorer shows this count live: open your transaction on Etherscan, Tronscan or Blockchair and it displays how many confirmations have stacked up so far, so you can compare it against what the operator needs.
Worked example with a hypothetical threshold: Bitcoin produces a block roughly every 10 minutes, so if an operator required, say, 3 confirmations, that's about 30 minutes before it credits, plus its own processing. The same threshold on Tron, where blocks arrive roughly every 3 seconds, clears in under a minute. That is why an identical confirmation rule feels instant on one chain and slow on another, and why a Bitcoin deposit that's only 20 minutes old usually isn't stuck, just early.
How many confirmations a deposit needs by network
Two numbers decide how long you wait: how fast the chain produces blocks, and how many of those blocks the operator wants before crediting. The block time is fixed by the protocol; the confirmation count is the operator's call, and it is usually higher than the network minimum because a casino is crediting real balance and wants the transaction to be effectively irreversible first. The figures below are realistic ranges drawn from each network's documentation and the defaults major exchanges publish, not casino marketing claims.
| Network | Approx. block time | Typical confirmations to credit | So crediting takes roughly |
|---|---|---|---|
| Solana (SOL/SPL) | ~0.4 s | finality in seconds | seconds |
| Tron (TRC-20) | ~3 s | ~20 | ~1 min |
| BNB Smart Chain (BEP-20) | ~3 s | ~15 | ~1 min |
| Polygon (PoS) | ~2 s | ~100+ | a few minutes |
| Ethereum (ERC-20) | ~12 s | ~12–35 | ~3–7 min |
| Litecoin | ~2.5 min | ~6 | ~15 min |
| Dogecoin | ~1 min | ~6–20 | ~6–20 min |
| Bitcoin | ~10 min | ~1–3 | ~10–40 min |
Block times are protocol-level properties of each chain; confirmation counts are typical receiver defaults, not fixed rules. Sources: Blockchain.com and Blockchair for Bitcoin/Litecoin/Dogecoin block data, Etherscan for Ethereum, Tronscan for Tron, Solscan for Solana, and each network's public protocol documentation. Verified 2026-06-23.
One detail trips people up: Polygon and similar high-throughput chains produce blocks fast but ask for a lot of confirmations, so "many confirmations" does not always mean "slow." It is the product of block time and confirmation count that matters, which is why a 100-confirmation rule on Polygon can still finish before a 3-confirmation rule on Bitcoin.
Why a deposit shows "pending"
Before any operator threshold even enters the picture, a deposit can sit pending for ordinary network reasons:
- Unconfirmed in the mempool. Your transaction has been broadcast but not yet included in a block. On a block explorer it shows zero confirmations and a "pending" or "unconfirmed" status. This is normal in the first minute or two.
- Fee too low for the current load. On Bitcoin and Ethereum, miners and validators prioritise higher-fee transactions. Set the fee too low during a busy period and yours waits behind others, sometimes for hours.
- Network congestion. When a chain is busy, every transaction confirms more slowly, even at a normal fee. The block time itself does not change, but blocks fill up and your transaction may not make the next one.
All three resolve on their own once the transaction confirms; the only fix for a stuck low-fee transaction is to wait, or to use a fee-bump (RBF) or accelerator on chains that support it. None of these are casino-side problems.
It's confirmed on-chain but still not credited — why?
This is the case that catches most people out, and it is genuinely under-explained. The explorer shows your transaction confirmed, even well past the operator's threshold, yet your casino balance hasn't moved. "Confirmed on-chain" and "credited to your account" are two separate steps, and a transaction can clear the first while failing the second. Here are the real causes, roughly in order of how often they're to blame:
- Below the operator's minimum deposit. Many operators silently ignore any deposit under a per-coin minimum. The money sits in their wallet, fully confirmed, but never reaches your balance because it's beneath the floor their system credits. See minimum deposit amounts.
- Wrong network. The same token can exist on several chains. USDT on Tron and USDT on Ethereum are different networks; an operator that only credits one won't see a deposit on the other, even though it confirmed perfectly on its own chain. See wrong network.
- Missing memo or destination tag. Coins like XRP, XLM and TON land in a shared operator wallet, and the memo is the only thing that links the deposit to you. Confirmed on-chain, but unattributed without the tag. See missing memo or tag.
- An internal or smart-contract transfer the operator can't detect. Most deposit systems watch for a normal on-chain transfer to your address. If the funds arrive a different way — moved inside an exchange's internal ledger and only settled to the operator in a batch, or pushed by a smart contract or a multi-step contract call rather than a plain wallet-to-wallet send — the operator's detection may not register it as your deposit. The transaction can look completely confirmed on an explorer while the casino's watcher never flags it. Sending from an exchange that uses internal transfers, or from a contract wallet, is the usual trigger. Recovery here almost always needs support and the transaction hash, because automated crediting has already passed it by.
- Operator processing delay, manual review or KYC hold. Some deposits are queued for a human check, a fraud screen, or a KYC verification step before the balance updates. The chain has done its job; the operator simply hasn't released the credit yet.
Notice that only the first item is about the amount and only the last is purely an operator delay. The middle three are routing problems: the money is on-chain but pointed somewhere the operator's deposit detection isn't looking.
How to check your own confirmations
You don't have to take the casino's word for it. Find your transaction hash (TXID) in the sending wallet or exchange, then paste it into the right explorer for that chain and read the confirmation count directly:
- Bitcoin, Litecoin, Dogecoin — Blockchair or Blockchain.com
- Ethereum and ERC-20 / BEP-20 / Polygon tokens — Etherscan (and its sister explorers for those chains)
- Tron and TRC-20 — Tronscan
- Solana — Solscan
The explorer is the source of truth for whether the network has done its part. If it shows your transaction well above the operator's threshold and the balance still hasn't moved, the wait is over and the cause is one of the routing or hold reasons above, not the confirmations.
Per-operator confirmation thresholds
How many confirmations each operator requires (by coin) is being verified first-hand and will appear on each operator's deposit guide as it's confirmed. We don't publish thresholds we haven't checked. In the meantime, the confirmation checker tells you whether your case should credit at all.
How long to wait, and when to contact support
A fair rule of thumb: give a deposit the network's normal window plus a generous buffer before treating it as stuck. For fast chains (Solana, Tron, BNB, Polygon) that's a few minutes; for Litecoin and Dogecoin, up to half an hour; for Bitcoin, up to an hour during busy periods. If you're still inside that window and the explorer shows confirmations climbing, you're waiting normally.
Once you're past it, work through the checks in order rather than messaging support straight away:
- Right network? A wrong-network send never credits, no matter how long you wait — see wrong network.
- Required memo or tag included? If not, see missing memo.
- Amount above the operator's minimum? See minimum deposit.
- Confirmations complete on the explorer but still nothing after the operator's window? Read the count directly on the explorer for your chain, and if it's well above the threshold, open a support ticket with the transaction hash, the coin, the network and your account username. That combination is what lets support trace and credit it — and it's exactly the message the deposit checker drafts for you.
Want deposits that credit fast?
Low confirmation requirements and fast payouts are part of why Duel is our default pick for crypto play.
FAQ
Why does my deposit say pending when the blockchain shows it confirmed?
Operators wait for their own threshold of network confirmations before crediting, which is usually higher than the single confirmation a block explorer shows first. Until that threshold is met, your balance won't update even though the transaction is visible on-chain.
How long should a crypto deposit take to credit?
It depends on the coin's block time and the operator's confirmation requirement. Fast chains like Solana or Tron can credit in seconds to a couple of minutes; Bitcoin can take 20-60 minutes because blocks arrive roughly every 10 minutes. If it's far past that, it may be stuck for another reason.
My deposit is way past the expected time — what now?
Confirm you used the right network and didn't miss a memo. If both are correct and confirmations are complete, contact the operator's support with your transaction hash.
The blockchain says my deposit is confirmed but the casino still hasn't credited it — why?
Confirmed on-chain is not the same as credited. The common causes are: the amount was below the operator's minimum deposit, you sent on a network the operator doesn't detect, a required memo or tag was missing, the funds came from an internal or smart-contract transfer that the operator's deposit detection skips, or the deposit is sitting in a manual review or KYC hold. Each has a different fix, covered below.
Related: run the deposit checker · below the minimum deposit? · cheapest network to deposit.