> For the complete documentation index, see [llms.txt](https://docs.sia.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sia.tech/legacy/your-sia-wallet/wallet-troubleshooting/my-deposit-or-withdrawal-didnt-go-through.md).

# My deposit or withdrawal didn't go through

This could happen with transactions involving your wallet, an exchange like Bittrex or Poloniex, or mining pools like Luxor or Siamining.

The first thing you should do is see if the transaction was added to the Sia blockchain. To do so, go to the [SiaStats Explorer](https://siastats.info/navigator) and paste the transaction ID into the search box in the upper right corner.

If your hash is not found in the database, then the transaction has not yet been added to the blockchain. it may need some time to confirm, or there may have been an issue with your transaction. Common issues include using an incorrect address or wallet downtime on the exchanges.

It can take over 10 minutes, and sometimes over an hour during peak times, for your transaction to be added to the blockchain.

If you are withdrawing from an exchange or a mining pool, and you do not see your transaction in the explorer within an hour or so, please file a support ticket with the exchange or pool.

If your transaction does appear in the explorer, that's a good sign. Your transaction should reach its destination shortly, but delays may still occur due to network or exchange issues.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sia.tech/legacy/your-sia-wallet/wallet-troubleshooting/my-deposit-or-withdrawal-didnt-go-through.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
