Where's my Monero? Diagnose a missing transaction

Give this page a transaction ID and it can tell immediately whether the payment ever reached the network at all, whether it is waiting in the mempool for a block, or whether it landed in a block but its output is still inside the 10-block consensus lock. Each of those is a fact about the chain, not about any particular wallet.

• Not found anywhere: the ID is wrong, or the transaction was never actually broadcast.
• In the mempool: accepted by the network, not yet mined - ordinary, and usually resolves within a couple of blocks.
• In a block, still locked: mined, but every Monero output waits 10 blocks (about 20 minutes) before it can be spent.

The other three all look identical from the outside - fully confirmed, funds unlocked - so this page asks the questions that tell them apart. Once a transaction is fully confirmed and unlocked on the chain, an explorer has nothing left to say - if a wallet still shows nothing, the cause is local to that wallet or to what was actually typed when it was sent. This page asks the questions that separate the three: is the receiving wallet's node behind the real chain tip; was the payment sent to a subaddress a restored wallet has not been told to scan; or was it sent to an address that was never the intended recipient's in the first place.

• Lagging node: the wallet has not scanned far enough yet to see a transaction that is already on the chain.
• Subaddress not scanned: a restored wallet only watches a limited range of subaddresses until it is told to look further.
• Wrong address: the funds went to an address that genuinely is not the recipient's.

Every other branch here can be checked against the chain. This one cannot: Monero deliberately hides the recipient of a transaction behind a one-time key, so no explorer - ours included - can look up who an output actually went to. If a lagging node and subaddress scanning are both ruled out, the honest next step is comparing the address that was used against the one the recipient actually controls, character by character, copied fresh rather than from a note or clipboard history.

The transaction ID is enough for the first three branches. For the second three, having the receiving wallet's currently displayed sync height next to a live chain height turns "maybe the node is behind" into a yes-or-no answer in seconds.

My transaction shows plenty of confirmations but my balance did not change. What now?

The chain side is done - the cause is local. Check, in order: whether the receiving wallet is fully synced to the current chain height, whether it was sent to a subaddress on a wallet that was restored from seed rather than continuously open, and finally whether the address used really was the recipient's.

Can this page look up my Monero address to see if funds arrived?

No, and neither can any other tool. Monero hides the recipient of a transaction by design - a transaction ID can be looked up, but not an address. That is exactly why the wrong-address branch is the one this page cannot confirm for you.

It says the transaction is not found at all. Did I lose the funds?

Almost certainly not lost - almost certainly never sent. A transaction ID the network has never seen usually means it was never actually broadcast, or the ID was copied wrong. Check with whatever produced it that the transaction was really submitted.