
The number of Monero confirmations needed for an exchange is not universal. The exchange sets its own deposit threshold, while the Monero protocol and wallet apply separate rules to transaction inclusion and spendability. Use the glossary below to identify which number an order page is showing, then follow the connection map to verify an XMR transfer without confusing a network confirmation with an exchange credit.
Short Answer: Check the Exchange Threshold, Not Just the Wallet
Official Monero guidance states that newly received funds require 10 confirmations before they become unlocked and spendable in a wallet. Monero targets a block approximately every two minutes, so 10 confirmations are often described as roughly 20 minutes. That is only an estimate: block production is probabilistic, and the transaction may also wait in the mempool before entering its first block. [1]
An exchange may require 10 confirmations, a different number, or additional internal processing before it marks an order as funded. Its threshold is an operational policy rather than a network-wide Monero constant. The controlling number is the one displayed in the current order or deposit instructions. Verification and compliance requirements can also vary by exchange direction and by the results of applicable checks.
- Zero confirmations: the transaction may have been broadcast but has not yet been included in a block.
- One or more confirmations: the transaction is in the blockchain, with later blocks increasing its depth.
- Ten confirmations: newly received XMR normally reaches the Monero wallet’s standard unlocked state. [2]
- Exchange credited: the service has recognized the deposit, applied its required threshold, and completed any relevant internal checks.
Essential XMR Exchange Glossary
- Monero (XMR)
- Exact meaning: Monero is a native coin recorded on the Monero blockchain; XMR is its ticker symbol. In plain language: it is the asset being sent, not a token issued on another blockchain. Where it appears: in wallets, exchange directions, balances, deposit instructions, and transaction records. Decision affected: select XMR on the Monero network rather than assuming that a similarly labelled asset on another network is interchangeable.
- Monero network
- Exact meaning: the peer-to-peer environment in which Monero nodes relay transactions, miners include them in blocks, and wallets interpret the resulting blockchain. In plain language: it is the system carrying the XMR transfer. Where it appears: in wallet network settings, node status, deposit instructions, and explorer data. Decision affected: verify that both the sending wallet and receiving service specify native Monero before broadcasting.
- Blockchain
- Exact meaning: the ordered chain of accepted blocks containing Monero transactions. In plain language: it is the shared record used to determine whether a transfer was included and how deeply it has been confirmed. Where it appears: indirectly in wallet synchronization information and directly through block heights or explorer records. Decision affected: distinguish a transaction merely waiting for inclusion from one already confirmed in a block.
- Exchange order
- Exact meaning: an off-chain instruction created with an exchange service, specifying the selected assets, direction, destination details, and applicable conditions. In plain language: it is the service’s record of what you intend to exchange. Where it appears: on the order page or in the order status. Decision affected: send only the requested asset, amount, and network to the address assigned to that order, within any conditions displayed before payment.
- Monero address
- Exact meaning: a public destination identifier used to receive XMR. Monero supports standard addresses, subaddresses, and integrated addresses; official documentation recommends subaddresses as the usual receiving option, while some automated services may use integrated addresses. In plain language: it tells the wallet where the payment is intended to go. Where it appears: in exchange deposit instructions and the sending wallet’s recipient field. Decision affected: copy the full address from the active order and verify it before sending, because blockchain transactions are not designed to be reversed. [3]
- Mempool
- Exact meaning: the pool of valid transactions known to a node but not yet mined into a block on the main chain. In plain language: it is the waiting area before the first confirmation. Where it appears: in node data, some wallets, and compatible explorers. Decision affected: if a txid is visible but the confirmation count remains zero, wait for block inclusion rather than immediately sending a duplicate payment. [4]
- Confirmation
- Exact meaning: a measure of a transaction’s depth in the blockchain after its inclusion in a block. Monero’s wallet RPC describes confirmations as blocks mined after the block containing the transaction. In plain language: every additional accepted block makes the payment more established in the chain. Where it appears: in wallet transaction details, exchange order status, wallet RPC output, or explorer results. Decision affected: compare the current count with the threshold stated by the exchange instead of assuming that “sent” or “confirmed” automatically means “credited.” [5]
- Unlocked balance
- Exact meaning: wallet funds deep enough in the Monero blockchain to be available for spending. Newly received transactions normally require 10 confirmations to reach this state. In plain language: the wallet can see incoming XMR before it is ready to spend again. Where it appears: as a distinction between total balance and unlocked balance in Monero wallet software. Decision affected: do not confuse visible funds with immediately reusable funds, particularly when planning a second transfer. [2]
- TXID or transaction hash
- Exact meaning: the identifier of a specific blockchain transaction. In plain language: it is the reference used to locate and discuss the transfer. Where it appears: in the sending wallet’s transaction history, support requests, node data, and explorers. Decision affected: save it after sending and use it to check inclusion and confirmations, but do not treat the presence of a txid alone as proof that the exchange has credited the correct order.
- Network fee
- Exact meaning: the mining fee attached to a Monero transaction for processing by the network. In plain language: it pays for submitting the on-chain transfer; it is not automatically the same as an exchange fee or quoted exchange cost. Where it appears: in the wallet’s send confirmation and transaction details. Decision affected: review the final amount sent to the exchange address and do not subtract or add fees manually unless the order instructions explicitly require it. Monero node documentation identifies the transaction fee as a mining fee recorded in atomic units. [4]
- Chain reorganization
- Exact meaning: a change in which recent blocks are accepted as the main blockchain, potentially removing and replacing blocks near its tip. In plain language: a very recent confirmation can be displaced if the network settles on a competing chain segment. Where it appears: mainly in node operations and service risk policies rather than ordinary wallet screens. Decision affected: exchanges wait for multiple confirmations instead of crediting every transaction as soon as it first enters a block. Monero’s node documentation notes that small reorganizations can occur and recommends confirmation depth when acting on valuable incoming payments. [6]
Connection Map: From XMR to a Verifiable Exchange Deposit
The terms form one process rather than separate definitions:
- Object → XMR coin. The transferable asset is native Monero, not a token representation on an unrelated chain.
- Network → Monero blockchain. The sending wallet broadcasts the transaction to the Monero network, where it initially may remain in the mempool.
- Action → send to the order address. The wallet constructs a transaction paying the address supplied for the active exchange order and attaches a network fee.
- Identification → TXID. After broadcast, the wallet provides a transaction identifier that can be used to monitor the transfer.
- Confirmation → block inclusion and depth. The first mined inclusion changes the transaction from unconfirmed to confirmed; later blocks increase its confirmation count.
- Network result → sufficient confirmation depth. At 10 confirmations, newly received XMR normally becomes unlocked under the standard Monero wallet rule. [2]
- Service result → order recognition and credit. The exchange compares the deposit with its order data, waits for its stated threshold, and may perform relevant internal or compliance checks.
- Final user check → completed order details. Confirm the output asset and destination shown for the order rather than relying only on the blockchain status of the incoming XMR.
Because Monero targets two-minute blocks, multiplying the remaining confirmations by two gives a rough network estimate, not a deadline. For example, five remaining confirmations suggest about ten minutes under target conditions, but actual block intervals and service processing can be shorter or longer. [1]
Do Not Confuse These Terms
XMR coin vs token
XMR is the native coin of the Monero blockchain. Calling it a token can encourage the false assumption that it can be sent over a selectable smart-contract network. The practical consequence can be choosing an unsupported asset or network. Use the exact XMR deposit instructions supplied for the order and never infer cross-network compatibility from a ticker alone.
Transaction vs exchange order
The transaction is the on-chain XMR payment; the order is the exchange service’s off-chain record. A transaction can have many confirmations while the order remains pending if the amount, address, selected direction, timing conditions, or required checks do not match. Conversely, an order number is not evidence that an XMR transaction was broadcast. Keep both identifiers.
Broadcast vs first confirmation
Broadcast means the wallet submitted the transaction to the network. Confirmation begins only after miners include it in a block. A transaction present in the mempool is not yet on the main blockchain, so repeatedly resending the payment can create a second transfer rather than accelerate the first one. [4]
Confirmed balance vs unlocked balance
A wallet may detect incoming XMR before those funds are spendable. The 10-confirmation unlock rule explains why a received transfer can appear in the total balance while remaining outside the unlocked balance. An exchange deposit threshold is a separate policy and should not be inferred from the sender’s wallet status. [2]
Network fee vs exchange charge
The network fee belongs to the Monero transaction and compensates miners. Any exchange charge, spread, or amount adjustment belongs to the service’s quoted conditions. Combining the two can cause an incorrect deposit amount or an inaccurate comparison between the amount sent and the amount expected.
Fee vs gas
“Gas” is terminology commonly associated with smart-contract platforms. A native Monero transfer uses a transaction or mining fee, not a separate gas token. The practical risk is buying or sending an unnecessary second asset because an interface or guide for another blockchain was applied to XMR.
Address vs Memo or Tag
A Monero receiving instruction may use a unique subaddress or an integrated address. Integrated addresses can contain an encrypted payment ID for automated payment matching, but a business identifier such as an order number is not automatically a Monero payment ID. Do not invent a Memo or Tag when none is requested, and do not omit any identifier explicitly supplied by the receiving service. [7]
TXID vs private transaction proof
A txid identifies the transaction, but Monero’s privacy design means a public lookup does not expose payment details in the same way as a transparent blockchain. Monero wallet tools can verify a payment using additional information such as the transaction key and destination address. Never publish sensitive proof material merely because someone asks for the txid; first verify what information legitimate support actually needs. [2]
Address vs seed phrase or private key
An address is intended to receive funds. A seed phrase or private spend key controls the wallet and must not be entered into an exchange order, explorer, support form, or unsolicited website. Anyone requesting wallet recovery secrets to “release confirmations” or “synchronize a deposit” is not performing a normal blockchain confirmation check.
Practical XMR Exchange Example
Suppose an order asks you to deposit XMR and shows a Monero address plus a required confirmation count. Before sending, open the current XMR exchange order and compare its asset, direction, address, required amount, and any displayed identifier with the wallet’s send screen. Confirm that the requested pair and direction are currently available; support for XMR does not mean that every possible pair, network, or route is offered.
Send only after the full address has been checked. Once the wallet broadcasts the payment, save the txid and return to the order status. If the transaction is still unconfirmed, wait for block inclusion. If confirmations are increasing but the order remains pending, compare the current count with the service threshold. Once that threshold has been reached, allow for order matching and any applicable checks before contacting support.
When support is necessary, provide the order identifier, txid, asset, amount, and approximate sending time through the service’s official channel. Do not send the wallet seed phrase, private keys, passwords, remote-access credentials, or unrelated identity documents in response to an unsolicited message.
How to Recognize the Terms in a Wallet or Explorer
- In documentation: search for “required confirmations,” “deposit confirmations,” “crediting threshold,” or “unlock.” The first three usually describe service policy; “unlock” may describe when received XMR becomes spendable.
- In a wallet: look for transaction status, txid, block height, confirmations, fee, total balance, and unlocked balance. Interfaces vary, so do not expect every wallet to use identical labels.
- In an explorer: use the txid to check whether the transaction is known, whether it has entered a block, and how many blocks have followed. A public explorer may verify chain inclusion without revealing the recipient and transferred amount as transparent ledgers typically would.
- On an order page: separate the deposit address, order identifier, expected amount, confirmation progress, and final order state. Similar-looking strings serve different purposes.
- In a support message: treat requests for seed words, private keys, wallet files, or advance payments to “unlock” a transaction as phishing indicators.
Safety Checklist Before and After Sending XMR
- Confirm that the order explicitly requests native XMR and that the selected exchange direction is currently available.
- Copy the address from the active order rather than from an old message or transaction history.
- Compare the beginning and end of the address after pasting, and use any full-address verification offered by the wallet.
- Check whether the service supplied an integrated address, unique subaddress, payment identifier, or other order-specific instruction; never improvise missing data.
- Review the amount and network fee before authorizing the irreversible transaction.
- Save both the exchange order identifier and the Monero txid.
- Wait for the service’s stated number of confirmations instead of treating the 10-confirmation wallet unlock rule as a guaranteed exchange threshold.
- Remember that a two-minute block target produces an estimate, not a fixed completion time.
- Use only the official order page and support channel; avoid links sent through unsolicited emails, advertisements, or direct messages.
- Verify the destination asset address before the exchange is completed, since sending the output to the wrong network or address may be irreversible.
The usable answer is therefore two-part: Monero wallets normally unlock newly received XMR after 10 confirmations, but the confirmations required to credit an exchange order are set by the receiving service. Read the threshold displayed for the specific order, monitor its txid until that count is reached, and distinguish blockchain completion from the exchange’s separate matching and verification process.


