You entered five trades and two cards came back: how to find the ones that are still yours

Every Enter that lands should become a card: the asset, the play name, the MON you put in, the MON the pool would hand back, and a Close button. The list is every open fill in this browser, from the wallet and from every vault address that has a notebook, sorted by size with the staking rows. If you signed five and you see two, three are either not in this browser’s notebook, not landed, or already sold. Those are different problems. The token balance tells them apart.

Where a card is stored

The notebook is local to the browser. A wallet fill is stored under your address. A vault fill is stored under the vault. A phone and a laptop do not share it. A cleared site storage does not keep it. The chain does not know about the notebook at all. It knows the tokens. If you open My money on a browser that never signed the entries, you will see staking and you will not see those cards, even while the wallet still holds the coins. The cards reappear only where the notebook was written, or not at all. The coins reappear wherever the wallet is connected.

Older builds hid fills of 10 MON or under behind a More row, and they read only the one vault that was currently bound. A second vault’s notebook was invisible. Both of those are gone. Small fills show. Every address that has a notebook is listed. If a card is still missing, it was not written, or it was deleted, or you are in a different browser.

The notebook can forget you. The token balance cannot, until something spends it.

Match hashes to coins

Take the activity list in the wallet, or the hashes you copied, and open each one. A successful swap into WBTC, WETH or cbBTC increased that token. A successful swap out decreased it. Add up what should be left. Then read the token balance on the explorer for your address and, separately, for the vault. If the sum of the cards’ implied tokens matches the balance, the notebook is complete and you are looking at all of it. If the balance is larger, you have coins with no card. They are still yours. You can sell them from the wallet with a swap, or wait until a card is rebuilt. If the balance is smaller, a sell you thought failed has already landed. Do not close the leftover card down to zero. You would be selling coins you do not have.

Why a landed trade never became a card

The card is written after the signature returns. If the wallet showed a hash and the page then threw the receipt timeout, older code treated that as failure and did not write the line, or wrote it and then deleted it. The swap could still have succeeded. That is the case the balance check is for. Newer code treats that timeout as a send and keeps the close removed. It cannot invent a card for a buy this browser never recorded. The hash can. File the hash, read the token, and decide whether you want the position. The page will not guess one into existence from a balance, because a balance does not remember which play, which stop, or which of three buys it came from.

Two cards can be one market

Two WBTC cards are two fills. They can share a pool and a wallet balance that is simply the sum. Closing one sells that fill’s quantity, not the whole balance. Closing both sells both. If the quantities in the notebook add up to more than the wallet holds, one of the quantities is a doubled read and the second close will revert. Trust the balance. Close once for the coins that are there.

What “3 unpriced” is not

The footnote that counts unpriced items is not a count of missing cards. It is a count of holdings with no MON value. A card can exist beside that footnote. Dust under a few MON sits in Other. Spare native MON is named and excluded. None of those three is a 50 MON fill that the list decided to skip. A 50 MON fill that you still hold is either a card or a token balance you have not matched to a hash yet.