Get EVM Transactions
Retrieve raw blockchain transactions for any EVM address (wallet or contract) via Sim Dune API with optional ABI decoding. Returns complete tx data: hash, block, timestamp, addresses, value, gas, input data, and logs. Set decode=true for human-readable function calls and events. Most recent first. Pagination: max 100/request, use nextOffset for older txs. Ideal for: transaction analysis, smart contract debugging, event extraction, building block explorers.
Catalog action Blockchain Data
Retrieve raw blockchain transactions for any EVM address (wallet or contract) via Sim Dune API with optional ABI decoding. Returns complete tx data: hash, block, timestamp, addresses, value, gas, input data, and logs. Set decode=true for human-readable function calls and events. Most recent first. Pagination: max 100/request, use nextOffset for older txs. Ideal for: transaction analysis, smart contract debugging, event extraction, building block explorers.
At a Glance
| Field | Value |
|---|---|
| Action ID | sim-dune-get-evm-transactions |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | sim-dune, blockchain, wallet, transactions, raw, decoded, logs, events, abi, debug, explorer, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
address | string | Yes | EVM address (wallet or contract) to get transactions for |
chainIds | array | No | Chain IDs to query (optional, defaults to all supported chains) |
decode | boolean | No | Include decoded function calls and event logs (default: false) |
limit | number | No | Maximum number of transactions to return (default: 100, max: 100) |
offset | string | No | Cursor for pagination (use nextOffset from previous response) |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
address | string | Yes | EVM address queried |
transactions | array | Yes | Raw transaction data |
hasMore | boolean | Yes | Whether there are more results available |
nextOffset | string | No | Cursor for next page of results |
requestTime | string | No | Request timestamp (ISO string) |
responseTime | string | No | Response timestamp (ISO string) |
warnings | array | No | Non-fatal warnings |
errors | object | No | Error details (if request failed partially) |
Examples
json{ "type": "sim-dune-get-evm-transactions", "payload": { "address": "0x0000000000000000000000000000000000000000" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/sim-dune-get-evm-transactions/test" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "inputs": { "address": "0x0000000000000000000000000000000000000000" }}'
Payload fields can use workflow expressions such as {{$trigger.body.amount}}, {{$nodes.fetch.result.price}}, and {{$props.asset}} when the value should come from a trigger, prior node, or reusable workflow prop.