> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blockgence.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor

> Block-by-block detection of possible attacks on the network: the pattern explained, who lost and which funds moved.

> [!NOTE]
>
> The application interface is in Spanish. Screens, tabs and buttons are referred to by their name in the application,
> followed by their English meaning.

Monitor analyzes the network block by block and flags the transactions in which a third party loses funds. Each flagged
transaction is analyzed with the exploit heuristics, and those that belong to the same actor are grouped into an
**incident**. Each incident explains in plain language what happened, who lost and why it was flagged. The technical
detail is presented collapsed.

It is available at **app.blockgence.com → Monitor**, with the organization's account. It is read-only.

![Monitor incident list](https://mintcdn.com/blockgence/jIDqBW86tOU_Ini-/images/products/monitor/list.png?fit=max\&auto=format\&n=jIDqBW86tOU_Ini-\&q=85\&s=e41c1c89050684063138575c631b3376)

Incident list with synthetic data.

## What it detects

Monitor analyzes the transactions in which a third party suffers a significant net loss. For each one, it evaluates who
gained, whether the called contract is new, whether there was a flash loan, how many transactions the signing account had
sent before and which exploit patterns appear.

Each incident has a **level**:

| Level | Meaning |
| - | - |
| **Posible ataque** (possible attack) | It combines more than one stage of an attack, or it is a large theft or a takeover. |
| **Señal suelta** (isolated signal) | A single stage. It matches the shape of many legitimate movements, such as an arbitrage or a self-withdrawal. It is shown in a separate tab. |

The stages evaluated:

| Stage | Indication |
| - | - |
| Preparation | A recently deployed contract, an attack executed when the contract is created, or a takeover. |
| Theft | The attacker's accounts retained what a third party lost, or a custodian lost funds to an attack contract. |
| Exit of funds | The funds were sent to an account with no history, or tokens minted in the attack were sold. |
| Funding | The origin of the attacking account's funds. **Not evaluated yet**, and the incident card states so. |

## Analyze an incident

**1. Select the tab**

**Posibles ataques** (possible attacks), **señales sueltas** (isolated signals), **confirmados** (confirmed),
**descartados** (dismissed) or **todos** (all). Each row shows who lost and how much ("… lost \~US\$820K"), the level,
the network, the date and the status: to review, confirmed or dismissed.

**2. Read the incident card**

The top of the detail shows the title, a one-sentence summary of what happened and the detected stages. Below are the
diagram of the funds moved (who ended up losing and gaining each token, and the movements between accounts) and the
reasons for flagging it.

**3. Review the technical detail**

For each transaction: the rule that opened the incident, with each required condition and the measured value (✓ met,
✗ not met, ? no data); the reason it entered the analysis; losses and gains by asset; the exploit signals; the
accounts attributed to the attacker; and what was not evaluated.

**4. Continue the investigation**

Each address offers **rastrear** (trace), which opens Investigation from that address, and **vigilar** (watch), which
adds it to Guard as an attacker's address. Each transaction opens its own page.

> [!NOTE]
>
> A condition without data is never considered met: it is shown as "no data".

![Incident detail](https://mintcdn.com/blockgence/jIDqBW86tOU_Ini-/images/products/monitor/detail.png?fit=max\&auto=format\&n=jIDqBW86tOU_Ini-\&q=85\&s=848617a02d01c7266c8c4db32ad16bb5)

Incident detail with synthetic data.

## Confirmed incidents and public detections

An incident remains **to review** until the Blockgence team confirms or dismisses it. Confirmed incidents can be
published in the **Detections** section of [blockgence.com](https://www.blockgence.com/en/detections): one alert per
incident, with the network and the transactions, without USD amounts or addresses.

## Scope and limitations

* **Ethereum only.** Other networks are not analyzed block by block.
* Not covered: losses below the detection threshold and cases the rules do not recognize, such as exploits through token
  minting, unpriced tokens, losses split across many small transactions, and attacks signed by automated accounts with
  thousands of transactions.
* The rules are measured against known attacks, but they **do not detect every case**, and a signal is not a verdict: an
  incident to review may correspond to a legitimate movement.
* Monitor **does not send alerts outside the application** and has no public API. To receive alerts on your own
  addresses, or to follow an attacker, use [Guard](https://docs.blockgence.com/en/products/guard.md).
* It does not freeze or block funds: it describes what happened on the network.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.