Get Wallet Activity
Retrieve decoded and categorized transaction history for any wallet address via Sim Dune API. Returns human-readable activity (transfers, swaps, approvals, NFT trades, staking, bridges) with timestamps, addresses, token amounts, and USD values. Most recent first. Pagination: default 20, max 100 items, use nextOffset for older activity. Ideal for: activity feeds, transaction notifications, audit trails, wallet behavior analysis.
Catalog action Blockchain Data
Retrieve decoded and categorized transaction history for any wallet address via Sim Dune API. Returns human-readable activity (transfers, swaps, approvals, NFT trades, staking, bridges) with timestamps, addresses, token amounts, and USD values. Most recent first. Pagination: default 20, max 100 items, use nextOffset for older activity. Ideal for: activity feeds, transaction notifications, audit trails, wallet behavior analysis.
At a Glance
| Field | Value |
|---|---|
| Action ID | sim-dune-get-wallet-activity |
| Category | Blockchain Data |
| Connector | Not required |
| Requires gas | No |
| Funds movement | None declared |
| Tags | sim-dune, blockchain, wallet, transactions, activity, history, transfers, swaps, approvals, decoded, feed, read |
Payload Schema
| Field | Type | Required | Description |
|---|---|---|---|
address | string | Yes | Wallet address to get activity for |
chainIds | array | No | Chain IDs to query (optional, defaults to all supported chains) |
limit | number | No | Maximum number of activities to return (default: 20, max: 100) |
offset | string | No | Cursor for pagination (use nextOffset from previous response) |
filterSpamTokens | boolean | No | Post-process results through the B3OS token filter service to remove spam and low-liquidity tokens from transfers. Default: true |
Result Schema
| Field | Type | Required | Description |
|---|---|---|---|
address | string | Yes | Wallet address queried |
activities | array | Yes | Transaction activities |
hasMore | boolean | Yes | Whether there are more results available |
nextOffset | string | null | No | Cursor for next page of results |
warnings | array | No | API warnings (e.g., unsupported chain IDs) |
Examples
json{ "type": "sim-dune-get-wallet-activity", "payload": { "address": "0x0000000000000000000000000000000000000000" }, "children": []}
bashcurl -X POST "https://api.b3os.org/v1/actions/sim-dune-get-wallet-activity/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.