> ## 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

> What the monitor detects on chain, block by block: possible attacks with the pattern explained, who lost and what moved.

Monitor follows the chain block by block and flags the transactions in which a third party loses funds. Each one is
analyzed with the exploit heuristics, and the compatible ones from 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 stays folded.

> [!NOTE]
>
> The app's interface is in Spanish. Screens, tabs and buttons are named as they appear, with their English meaning.

Open it from **app.blockgence.com → Monitor**, with your 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)

The incident list, with synthetic data.

## What it detects

A transaction enters the analysis when a third party loses at least \*\*US$100,000** net in it, or at least US$10,000 if
the transaction took a flashloan. That transaction is then analyzed: who gained, whether the called contract is new,
whether there was a flashloan, how many transactions the signer had sent before and which exploit patterns show up.

Each incident has a **level**:

| Level | What it means |
| - | - |
| **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** (loose signal) | A single stage. It looks like many normal movements, such as an arbitrage or a self-withdrawal. It is still shown, in its own tab. |

The stages it looks at:

| Stage | What marks it |
| - | - |
| Preparation | A freshly deployed contract, an attack that runs when the contract is created, or a takeover. |
| Theft | The attacker's accounts kept what someone else lost, or a custodian lost funds to an attack contract. |
| Exit | The funds went to an account with no history, or what was minted was sold. |
| Funding | Where the account's money came from. **Not looked at yet**, and the card says so. |

## Read an incident

**1. Pick the tab**

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

**2. Read the card**

At the top of the detail: the title, what happened in one sentence and the stages as chips. Below, the diagram of what
moved (who ended up losing and gaining each token, and the account-to-account movements) and the reasons, in short
sentences.

**3. Open the technical detail if you need it**

For each transaction: the rule that opened the incident with every condition it required and the measured value
(✓ met, ✗ not met, ? no data), why it entered the analysis, who lost and who gained by asset, the exploit signals, the
accounts it treats as the attacker's and what it did not evaluate.

**4. Follow up from there**

Every address has **rastrear** (trace: opens Investigation from that address) and **vigilar** (watch: loads it in Guard
as an attacker's wallet). Every transaction opens its own page.

> [!NOTE]
>
> A condition without data is never taken as 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)

The detail of an incident, with synthetic data.

## Confirmed incidents and public detections

An incident stays **to review** until someone at Blockgence 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.

## What it does not cover

* **Ethereum only.** Other networks are not monitored block by block.
* What falls outside the threshold and the rules: exploits by token minting, unpriced tokens, losses split across many
  small transactions, and attacks signed by bots with thousands of transactions.
* The rules are measured against known hacks, but they **do not catch every one**, and a signal is not a verdict: an
  incident to review can be a legitimate movement.
* Monitor **does not send alerts outside the app** and has no public API. To get alerts on your own wallets, or to
  follow an attacker, use [Guard](https://docs.blockgence.com/en/products/guard.md).
* It does not freeze or block anything: it describes what happened on chain.


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