Introducing Transaction History: Complete wallet activity, directly from Turnkey

Today, Turnkey is adding Transaction History to its Transaction Management suite, giving developers a native way to read the full onchain history of every address they secure, through the same infrastructure they already use to sign and send.
Building a wallet product has always meant assembling more moving parts than it should. Previously, teams would secure keys in one system, broadcast through another, track balances somewhere else, and then reach for a separate indexer or a set of per-chain APIs just to show a user what they have done.
Turnkey’s Transaction History closes that gap. Applications can now surface a complete activity feed, reconcile an agent's actions, or produce an audit trail directly from Turnkey, with no extra data pipeline to run.
Transaction History: The missing piece of transaction management
Turnkey's Transaction Management suite already covers the parts of the lifecycle that move value: transaction construction, signing, broadcasting, gas sponsorship, and real-time balances. Transaction History completes the picture by providing a record of everything a wallet has done.
Starting today, a developer using Turnkey for any part of transaction management can access history with a single API call. There are no new dependencies to add and no separate providers to integrate.
One platform now covers the full transaction lifecycle: constructing and signing a transaction, broadcasting it, tracking its balance impact, and showing its history.
What Transaction History returns
The Transaction History API returns a normalized view of a wallet's onchain activity, with everything a team needs to display or reconcile a transaction in one response.
Each record includes the core details of the transaction itself:
- Transaction hash
- Block information
- Status
- Network fee
It also includes full transfer details for the value that moved:
- Sender and recipient addresses
- Direction of the transfer
- Asset involved
- Counterparty
Because the response is normalized across EVM and Solana, a team can render an activity feed the same way regardless of the underlying chain.
One API across EVM and Solana
Transaction history has traditionally been one of the more tedious things to build, because every chain exposes its data differently. Reading an Ethereum wallet's history looks nothing like reading a Solana wallet's, and supporting both usually means maintaining two integrations, or paying a third-party indexer to smooth over the difference.
Turnkey removes that work. Transaction History provides one API for both EVM and Solana (SVM), so there is no chain-specific code to write and no external indexer in the loop.
Support currently spans EVM and SVM, with more networks planned. As Turnkey adds coverage, the same endpoint and the same response shape extend to new chains, so teams do not rewrite their integration each time.
Why Transaction History matters
Payment apps rely on a receipt trail, treasury and compliance teams need an auditable record, and agent systems have to reconcile what they executed against what actually landed onchain.
Without native history, teams answer that question with another integration or infrastructure they’re forced to own. An in-house indexer has to be built, scaled, and kept in sync with every chain. A third-party provider adds another vendor, another bill, and another dependency to reconcile against the wallet's true state.
Transaction History brings that record into the same system that already secures the wallet and broadcasts its transactions. The result is a complete wallet stack with fewer external pieces to keep aligned.
Turnkey: Full-service transaction management
Every layer of Turnkey's transaction management suite above the RPC, from private key management and signing through broadcasting, balances, and now history, is run by Turnkey, and that has real consequences for the teams building on it.
It means one source of truth for a wallet's state, fewer integrations to secure and monitor, and a history that stays consistent with the same wallets, policies, and transactions Turnkey already manages.
For developers, that translates into one platform for signing, sending, balances, and history. For end users, it makes wallet experiences feel whole: they can see what they hold and everything they have done, in the same product.
Get started with Transaction History
Transaction History is available now for wallets Turnkey secures across EVM and Solana, with more network support on the way.
Add a single API call to surface every wallet’s transaction history, complete with hashes, block details, status, fees, and transfer information, using the same infrastructure you already use for signing, broadcasting, and balances.
Read the transaction management docs to start building with Transaction History, and get started with Turnkey today.
Related articles

Introducing MFA and Scoped Sessions: Programmable, per-action security for any wallet operation
MFA require an additional authenticator before high-risk actions, and Scoped Sessions restrict a single session to specific actions.

Turnkey expands Monad and Optimism support (TX management, gas sponsorship, balances)
Today Turnkey announces expanded infrastructure support for Monad and Optimism, including balances, transaction management, and gas sponsorship.

