You sent XMR to a swap deposit address, copied the transaction ID, and found a public page showing a hash and fee but no recipient or amount. That is not automatically a failed payment. Copy the full TxID, compare the destination with the live order, check the transaction on a Monero explorer, and give official support the Order ID and TxID before considering any proof or resend.
Summary: A Monero TxID proves that a transaction exists, but a public explorer normally cannot display the recipient and amount like a Bitcoin explorer can. Keep the live order details, send the full TxID with the Order ID to official support, and generate a transaction proof for the order deposit address only if support asks. Never send a seed, spend key, view key, wallet password, or a second deposit.
Monero is private by design: ring signatures hide the real input, stealth addresses hide the recipient, and RingCT hides the amount. A public transaction page can therefore look incomplete even when the network has accepted the transaction.
This guide proves one XMR payment to one swap order. Keep the order open and use the address shown inside it. For the general process of locating a transaction ID, see how to find and check a crypto TxID.
How to copy the TxID from the sending wallet
Open the wallet that sent the XMR, select the outgoing transfer for this order, and copy the complete transaction ID. Do not retype, shorten, or copy only part of it. Keep the original text in a private note.
Record the complete MarketExchange Order ID, full TxID, deposit address shown in the live order, amount shown by the sending wallet, and status. Use the exact address from the live order, not one from an old order, chat, or search result. The Order ID identifies the exchange order; the TxID identifies the Monero transaction.
Live order: Order ID + deposit address → sending wallet: full TxID + amount + status → network: transaction page and confirmations.
- Open the live MarketExchange order and keep its Order ID visible.
- Copy the deposit address exactly as displayed.
- Select the outgoing XMR transfer in the sending wallet.
- Copy the entire TxID using the wallet’s copy control.
- Paste it into a private note and compare it with the wallet display.
- Record whether the wallet shows pending, in pool, or included in a block.
A screenshot is only a personal record. The full TxID copied from the wallet is the useful starting point for support and any later proof. Do not create a new order or send again because the first transaction is not immediately visible. For a stuck order, use the stuck crypto swap order status checklist.
Why a public XMR explorer hides the recipient and amount
Use a Monero explorer to answer a limited question first: does the TxID exist in the transaction pool or in a block? A public page may show the hash, fee, block information, confirmations, rings, and stealth outputs. It can show the amount as ?. That question mark is expected for a private RingCT amount and is not evidence of an empty payment.
Unlike a Bitcoin explorer, a Monero explorer normally cannot connect public inputs and outputs with readable addresses and amounts. The recipient address and amount are hidden from ordinary public inspection.
| Explorer result | Meaning | Action |
|---|---|---|
| TxID found in the pool or a block | The network has seen it | Save the page and do not resend |
| Confirmations and fee visible | Public network data is available | Keep the TxID with the Order ID |
| Recipient is not shown as the order address | Stealth addressing is expected | Use an address-bound proof if requested |
| Amount appears as ? | The RingCT amount is hidden publicly | Do not treat it as zero |
| TxID not found yet | It may still be propagating or not broadcast | Check the sending wallet |
The explorer is a network-status check, not complete payment proof. It can show that a transaction exists, but it normally cannot prove from the public page alone that the transaction paid this order’s deposit address or how much was sent there.
Monero targets roughly two-minute blocks. Incoming outputs also have a ten-block spendability lock at the protocol level. That is not a MarketExchange service-level promise or order completion time. Older transactions can have different ring sizes; you do not need to interpret ring members to prove a swap.
Do not paste a private view key or transaction key into a random explorer to reveal hidden fields. Some explorer forms warn that an address and view key, or an address and transaction private key, are sent to the server. That exposure is unnecessary for an instant-swap support case.
How to share the Order ID and TxID with official support
Begin with the smallest useful support packet: the complete MarketExchange Order ID and complete XMR TxID through the official support channel. Add the deposit address exactly as shown in the order if support requests it. A message such as “XMR sent, explorer shows the TxID, please verify the deposit” is enough to start.
Use the route linked from MarketExchange support and watch for impersonators. Someone contacting you through an unofficial account is not verified merely because they know your Order ID. Never give a stranger remote access to your wallet.
Workflow: Open live order → copy Order ID and deposit address → copy full TxID from the sending wallet → check TxID on a Monero explorer → send Order ID + TxID to official support → generate an address-bound proof only if requested → wait for the order update.
If support asks for a current Monero transaction proof, the relevant wallet command is:
get_tx_proof <txid> <address> [<message>]
The address must be the deposit address for this specific order. If support supplies a message, use that exact message. A transaction proof is a signature tied to the TxID and destination address; it does not reveal your secret key.
The corresponding check command is:
check_tx_proof <txid> <address> <signature_file> [<message>]
Some wallet interfaces provide a graphical proof screen with fields for Transaction ID, Address, optional Message, and Generate. Menu names vary, so rely on those fields rather than assuming identical navigation.
There is also a legacy transaction-key method:
get_tx_key <txid>
It may help in a dispute, but it is not the same as a transaction-proof signature and may be unavailable if the wallet did not retain transaction information. Transaction keys are stored locally and cannot be reconstructed from the blockchain. Start with Order ID + TxID and follow one verified support conversation.
Checklist: never send spend keys, a seed, or a view key
The seed, wallet password, and spend key stay private. A spend key can authorize spending, and the seed can restore control of the wallet. Never send either to support, paste either into a browser, or enter either into a verification form.
A view key can allow inspection of incoming transactions associated with an address, but it is not proof of one outgoing payment to one swap order. It can also reveal more wallet history than necessary. It is not the default evidence packet.
| Item | Purpose | Send to swap support? |
|---|---|---|
| Order ID | Identifies the MarketExchange order | Yes, through official support |
| TxID | Identifies the Monero transaction | Yes, through official support |
| Deposit address | Identifies the intended proof recipient | When needed |
| Transaction proof signature | Connects the TxID with the specified address | Only if requested |
| View key | May expose incoming wallet history | No, not by default |
| Spend key, seed, or password | Controls or restores funds | Never |
Do not confuse get_tx_proof with get_spend_proof. A spend proof can demonstrate that you created a transaction using your spend key, but the recipient address is not part of that command. For a swap deposit, the important question is whether the payment went to this order’s deposit address.
Do not confuse a transaction proof with a transaction key either. The older transaction-key method can reveal payment information to a verifier and may reveal change information when the verifier knows your address. A generated proof signature confirms the specified transaction and address without handing over the underlying secret.
A MarketExchange Order ID is not a Monero payment ID. Do not invent a payment ID, add a long payment ID, or assume that an order number belongs in the wallet’s payment field unless the live order explicitly says so. An integrated address is not the same thing as an exchange order number.
When to wait before you resend
Let the first transaction finish its network path before deciding about another payment. If the TxID is visible in the pool or a block, preserve it and wait for official order handling. If the wallet shows pending and no explorer can find it, verify that the wallet is online, the transfer was broadcast, and the TxID came from the correct transaction.
Use this decision checklist:
- TxID found in the pool: save the explorer URL, keep the order open, and do not resend.
- TxID included in a block: send the Order ID and TxID to official support if the order has not updated.
- TxID has confirmations: do not infer the hidden recipient or amount; provide proof only if requested.
- TxID not found: return to the sending wallet, confirm broadcast, and wait for propagation.
- Address or amount mismatch: preserve the evidence and ask support what options apply.
Confirmation is not the same as completion. A proof can show that funds were directed to a specified address while the order still requires processing or other operational checks. An explorer page cannot tell you that an output is still spendable, and a proof does not guarantee that funds are unlocked, unspent, or available after processing.
Do not resend because a search result shows no useful preview, an explorer displays a question mark, or support takes time to reply. Keep a private record of the Order ID, TxID, explorer URL, support case, and any proof file. The goal is to prove one payment to one recipient, not to make your wallet transparent.
Frequently asked questions
Why is my XMR TxID blank on Google?
Google is not a Monero payment verifier, and search indexing is not a reliable transaction check. Open a Monero explorer directly, paste the complete TxID, and check whether it is in the pool or a block. If it is not found, check the sending wallet’s broadcast status before resending.
Why does the Monero explorer show the amount as a question mark?
Monero uses RingCT to hide transaction amounts from public observers. A question mark is normal on a public transaction page and does not mean the transfer had no amount. The destination and amount require the appropriate wallet proof process.
Do I need to send a view key to prove my swap payment?
No. Start with the Order ID and full TxID. If official support asks for evidence, use a transaction proof tied to the order’s deposit address. A view key can expose incoming wallet history and is not the normal minimum proof. Never send a spend key, seed, or wallet password.
Is XMR slower than BTC for a swap?
Do not compare the coins using one guaranteed time. Monero targets roughly two-minute blocks and has a ten-block incoming-output lock at the protocol level, but that is not a MarketExchange completion promise. Check the actual TxID and order status instead of sending a duplicate.
What is the difference between get_tx_proof and get_spend_proof?
get_tx_proof uses a TxID and destination address to create a signature associated with payment to that address. get_spend_proof proves that you created the transaction using your spend key, but it does not include the recipient address in the command. For a swap deposit, use the order deposit address and ask official support which proof it needs.
Can a transaction proof guarantee that my order is complete?
No. A proof can connect a transaction with an address, but it does not guarantee that the output is spendable or that the order has completed. Send it only when requested, then follow the order status and official support response. Do not resend while the original transaction remains live.
What should I do if someone claiming to be support asks for my seed?
Stop responding and do not share it. A seed, spend key, and wallet password are never required to identify a swap payment. Use the official MarketExchange support page and provide only the Order ID and TxID at first. If you already disclosed a wallet credential, move funds to a secure wallet immediately using a trusted device.
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.