# Tracking unstake requests

1. **Monitor Events on the Blockchain**

The unstake request process typically involves sending a transaction to the smart contract that initiates the unstaking. The contract may emit events (messages) related to the **Unstake Request**, which can be tracked on the blockchain. Look for events such as:

* `OP::UNSTAKE`: When the **Unstake Request** is initiated, a message with the `OP::UNSTAKE` operation code will be sent. This message will contain details about the unstake request, such as the amount of TON and jettons (currently unused) to be unstaked, the owner's address, and the index of the request.

2. **Invoke** **`get_unstake_data()`** **method in** **Unstake Request** contract. By invoking this method you can retrieve the details of an unstake request. When **Unstake Request** sends message to **Financial** with `OP::UNSTAKE` it sets `unlock_timestamp` equal to `0`.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bemo.fi/developers/bemo-v2/tracking-unstake-requests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.