Skip to main content
Use transaction history to audit what your agent has done during a session — for example, calculating total fees paid, verifying that a swap executed correctly, or building a trade log.

List Transactions

Get transaction history with asset changes.
def transactions() -> TransactionsResponse
Response:
  • success (boolean): Whether the operation succeeded
  • data (array): Array of asset changes
    • network (string): Network identifier
    • transactionHash (string): Transaction hash
    • from / from_ (string): Sender address
    • to (string): Recipient address
    • amount (string): Amount transferred (string to preserve precision)
    • token (string | null): Token contract address (null for native tokens)
    • tokenId (string | null): Token ID for NFTs (null for fungible tokens)
    • tokenType (string): Token type (“native”, “ERC20”, “ERC721”, etc.)
    • tokenUsdPrice (string | null): Token price in USD at transaction time
    • timestamp (string): Transaction timestamp
  • error (string | null): Error message (on failure)
Example:
result = agent.transactions()
if result.success and result.data:
    agent.log(f"Found {len(result.data)} asset changes")

    outgoing = [c for c in result.data if c.from_ == agent.sessionWalletAddress]
    agent.log(f"Outgoing transfers: {len(outgoing)}")

Notes

  • Indexing speed varies by chain and may have a delay, so new transactions may not appear here immediately.
  • Amounts are strings to preserve precision for large numbers.
  • Network format: "ethereum:{chainId}" for EVM chains, "solana" for Solana, "hypercore:perp" and "hypercore:spot" for Hyperliquid.
  • The sender field is from in TypeScript and from_ in Python (since from is a reserved keyword).
  • tokenType values: "native", "ERC20", "ERC721", "ERC1155", "SPL".
  • tokenUsdPrice may be null if the price was not available at indexing time.

See Also

  • Positions — Check current balances instead of inferring from history
  • Swap and Bridge — Execute swaps that generate transaction records
  • Error Handling — Handle failures in transacting methods that generate history