Get Transactions by Address
get_transactions_by_addressRead-only
Retrieves native currency transfers and smart contract interactions (calls, internal txs) for an address.
**EXCLUDES TOKEN TRANSFERS**: Filters out direct token balance changes (ERC-20, etc.). You'll see calls *to* token contracts, but not the `Transfer` events. For token history, use `get_token_transfers_by_address`.
A single tx can have multiple records from internal calls.
Requires an `age_from` date to scope results for performance and relevance.
**SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| age_to | No | End date and time (e.g 2025-05-22T22:30:00.00Z). Adding this bounds the upper end of the date range started by `age_from`. | |
| cursor | No | The pagination cursor from a previous response to get the next page of results. | |
| address | Yes | Address which either sender or receiver of the transaction | |
| methods | No | A method signature to filter transactions by (e.g 0x304e6ade). Filters the (optionally date-bounded) results to a specific method signature. | |
| age_from | Yes | Start date and time (e.g 2025-05-22T23:00:00.00Z). Alone, returns all transactions to/from the address since this date. | |
| chain_id | Yes | The ID of the blockchain | |
| session_id | No | Opaque session identifier. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The main data payload of the tool's response. | |
| notes | No | A list of important contextual notes, such as warnings about data truncation or data quality issues. | |
| pagination | No | Pagination information, present only if the 'data' is a single page of a larger result set. | |
| content_text | No | Optional human-readable summary used for MCP content responses. | |
| instructions | No | A list of suggested follow-up actions or instructions for the LLM to plan its next steps. | |
| data_description | No | A list of notes explaining the structure, fields, or conventions of the 'data' payload. |