# Transaction Monitoring

> Address transaction history with filtering, decoding hints, and pagination.

- canonical: <https://ai.tatum.io/capabilities/transaction-monitoring>
- category: `data`
- risk: `low`

## Canonical recipe

End-to-end procedure: [incoming-payment-monitor](https://ai.tatum.io/workflows/incoming-payment-monitor). This capability page is the hub (tools, OpenAPI, examples).

## Why agents use it

Lets agents reconstruct what happened to an address without scanning blocks.

## MCP tools

- `get_transaction_history`
- `get_block_by_time`

## OpenAPI references

- `/openapi/blockchain-data.json` (tag: `Transactions API`)

## Docs

- <https://docs.tatum.io>

## Notes

## Canonical recipe

For ongoing monitoring prefer [Incoming Payment Monitor](/workflows/incoming-payment-monitor) (webhooks). For historical reconstruction use `get_transaction_history` via MCP or the Transactions API.

## Risk

Read-only. Be conservative with very wide time ranges on busy chains.