The Transaction Lifecycle Dashboard is in early access. Request early access!
The Transaction Lifecycle Dashboard gives you full visibility into every step of a Wallet API transaction from preparation to confirmation and helps you debug failures with AI-powered error explanations.
When you send a transaction through the Wallet API, it goes through multiple steps:
- Prepare —
wallet_prepareCallsprepares the transaction for submission - Send —
wallet_sendPreparedCallssubmits the prepared transaction onchain - Track —
wallet_getCallsStatuspolls for confirmation or failure
A failure at any step can be difficult to diagnose from raw logs alone. The Transaction Lifecycle Dashboard groups all steps by Call ID so you can see exactly where things went wrong — and why.
See every step of a Wallet API call grouped by Call ID, with status, duration, and full request/response payloads
Get plain-language explanations of why a transaction failed, along with specific remediation steps
Filter by status, app, network, and time range to find the exact transactions you're looking for
Inspect full JSON request and response bodies for each step, with copy support
- Open the Alchemy dashboard
- In the left sidebar, navigate to Tools > Logs
- Click the Wallet API Logs tab
Direct link: dashboard.alchemy.com/logs/wallet-api
You can also access logs scoped to a specific app by navigating to Apps > [Your App] > Logs > Wallet API Logs.
Select any row in the log table to open the Transaction Details panel on the right. It shows:
- Call ID — The unique identifier linking all steps of the transaction
- Status — Current state of the transaction (e.g., Confirmed, Pending, Prepare Failed)
- App & Network — Which app and network the call was made on
- Step timeline — Each Wallet API method call shown as an expandable card with status, duration, and full request/response JSON
Click on any step to expand it and inspect the full request and response payloads.
| Status | Description |
|---|---|
| Confirmed | Transaction successfully included onchain |
| Pending | Transaction submitted and awaiting confirmation |
| Preconfirmed | Transaction detected but not yet finalized |
| Prepared | Transaction prepared but not yet sent |
| Sent | Transaction sent and awaiting status |
| Cross Chain Pending | Cross-chain transaction in progress |
| Prepare Failed | Transaction failed during preparation (e.g., validation error) |
| Send Failed | Transaction failed during submission |
| Status Failed | Failed to retrieve transaction status |
| Offchain Failure | Transaction failed offchain before reaching the network |
| Onchain Failure | Transaction was included onchain but reverted |
| Partial Failure | Some calls in the batch succeeded while others failed |
| Cross Chain Refunded | Cross-chain transaction was refunded |
| Unknown | Transaction status could not be determined |
When a transaction step fails, the detail panel displays the error message and an Explain this error button.
Clicking the button sends the error context to an AI model that analyzes the failure and returns:
- Error category — A classification such as Validation Error, Sponsorship Failure, Session Key Error, Signing Error, or Contract Error
- What happened — A plain-language description of the root cause
- How to fix — Specific steps to resolve the issue
AI-generated explanations are provided as guidance and may not always be accurate. Always verify the details independently before making changes to your integration.
Validation Error
The transaction failed input validation before reaching the network. Common causes include malformed addresses, invalid calldata encoding, or missing required fields. Check your wallet_prepareCalls request payload against the API reference.
Sponsorship Failure
Gas sponsorship was rejected by the gas manager policy. Verify that your gas policy is active, has sufficient balance, and that the transaction meets your sponsorship rules.
Session Key Error
The session key used to sign the transaction is invalid, expired, or does not have permission for the requested action. Review your session key configuration.
Signing Error
The transaction signature was rejected or could not be produced. This can happen when the signer is not authorized for the account, the signing method is incompatible, or the signer service is unavailable.
Contract Error
The target contract reverted the transaction. This typically indicates an issue with the contract call itself — check the calldata, function parameters, and contract state.
Use the filter bar above the log table to narrow results:
- Time range — Choose from presets or set a custom range.
- Statuses — Multi-select filter to show only specific transaction states (e.g., failures only)
- Apps — Filter by a specific app when viewing across all apps
- Networks — Filter by blockchain network
- Send transactions — Learn how to send Wallet API transactions
- Sponsor gas — Eliminate gas fees for your users
- Common errors — Reference for frequently encountered issues