> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/features/key-features/lock-explorer.md).

# Lock Explorer

Lock explorer makes it easy to identify blocking sessions during blocked session issues, along with the associated queries and locks.

By continuously monitoring lock activity, Datasentinel offers insights into your database’s state and assists you in addressing issues by generating blocking scenarios that give comprehensive information about lock activity during blocked session incidents.

## How it Operates

Lock explorer is enabled by default and requires a minimum agent version of v3.2.

Datasentinel performs a check every minute to determine if there are any blocked sessions. If a blocked session duration exceeds the specified delay (default is **30s**), a blocking scenario is generated and sent to the platform.

A blocking scenario includes the identification of the blocking session, the locks held, the current query at the time of check, and the properties of the blocked sessions.

The blocking scenario is then updated every minute until it is resolved.

{% hint style="info" %}
Lock monitoring can be enabled or disabled and the delay can be adjusted through the agent [Agent CLI](about:blank/agent/CLI.html#agent-cli) or [Agent API](about:blank/agent/API.html#agent-apis).
{% endhint %}

## Visualization

When a blocking scenario occurs, a graphical annotation is added to the main dashboards to highlight the problem. This annotation displays information about the blocking session and the number of blocked sessions. By clicking on the dashboard link, you can access more detailed information.

The **Blocking Scenarios** dashboard presents an overview of current session activity in the main graph.

The bottom portion of the dashboard is split into two sections.

On the left, you will see a list of all blocking scenarios that occurred during the selected time frame. Simply click on a scenario to access its detailed information.

The information displayed for each scenario includes:

* Details of the blocking session, including its current query and the locks held at the time of the scan made by Datasentinel.
* The number of blocked sessions and details about each, including the waiting lock and current waiting query.

## Interactive Demo

{% @arcade/embed url="<https://app.arcade.software/share/1TJNUGSvNRHMRo6D3m3H>" flowId="1TJNUGSvNRHMRo6D3m3H" %}


---

# 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.datasentinel.io/manual/features/key-features/lock-explorer.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.