list_eth_transaction_history for EVM chains and list_sol_transaction_history for Solana. Full request/response schemas, cURL examples, and SDK snippets can be found in the API reference.
Prerequisites
- The queried
addressmust belong to a Turnkey wallet account. Standalone private-key addresses are not supported. - Pass the network as a CAIP-2 identifier (
caip2). For Solana, human-readable aliases such assolana:mainnetandsolana:devnetare accepted and normalized to canonical CAIP-2 values by the API.
EVM transaction history
list_eth_transaction_history takes an organization ID, wallet account address, and EVM caip2 chain ID (for example eip155:1 for Ethereum mainnet or eip155:8453 for Base). Supported chains are listed in the API reference.
Each item in transactions is ordered newest first and includes:
transactionHash,block(number, hash, RFC 3339 timestamp), andstatus(CONFIRMEDorFINALIZED)from, optionalto, andorigin(for exampleTURNKEYfor Turnkey-submitted transactions)feewith atomicamountandcaip19asset identifiertransfers[]withdirection(IN/OUTrelative to the queried address),asset, atomicamount,counterparty, and optionaldisplaystrings for UI- Optional
turnkeymetadata when Turnkey submitted the transaction:sponsored,activityFingerprint, andsubmittedAt
transfers[] for value movement; to reflects the transaction destination (such as a called contract) and may differ from transfer counterparties.
Solana transaction history
list_sol_transaction_history uses the same request shape: organization ID, wallet account address, and Solana caip2 (canonical mainnet/devnet IDs or solana:mainnet / solana:devnet aliases).
Solana responses mirror EVM items where applicable, with chain-specific fields:
signatureinstead oftransactionHashfeePayer— the account that paid the transaction fee (first signer in the message)signers[]— each signer’saddressand whether the account waswritablein the message
transfers, fee, and turnkey follow the same semantics as EVM history.
Pagination
Results are cursor-paginated via optionalpaginationOptions (limit between 1 and 100, default 10). Each response includes a pageInfo block:
hasNextPage/hasPreviousPageindicate whether more results exist in either direction.- Pass
pageInfo.endCursoras the next request’spaginationOptions.afterto fetch older transactions (continue paging down the newest-first list). - Pass
pageInfo.startCursoraspaginationOptions.beforeto fetch newer transactions. - Cursors are opaque and valid only for the same
addressandcaip2query. Do not construct or modify them.
@turnkey/sdk-server:
listSolTransactionHistory with the same pagination pattern.
SDK example
See thewith-transaction-history example in the SDK repo for runnable EVM and Solana scripts with interactive prompts and multi-page fetching.
Next steps
- List Eth transaction history and List Sol transaction history in the API reference
- Balances for current asset balances on supported chains
- Broadcasting transactions for submitting new transactions through Turnkey