get
https://public-api.birdeye.so/blockchain/v1/transaction/detail
Returns details for a Solana transaction signature.
Recent Requests
Log in to see full request history
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Loading…
- Returns a detailed Solana transaction view, including signatures, signers, fees, compute usage, and balance changes.
- This endpoint is best for transaction forensics and protocol debugging, not just simple transfer lookups.
sol_balance_changes,token_balance_changes,instructions, andlogsmay be large on complex transactions.- Use the exact Solana signature in
signature; this is not a generic cross-chain transaction endpoint.
- Standard
- Lite
- Starter
- Premium
- Business
- Enterprise
Solana
Use Cases 💡
- Investigate failed or suspicious Solana transactions with balance deltas and execution metadata.
- Reconstruct fee spend, priority-fee usage, and compute-unit consumption for transaction analytics.
- Debug protocol integrations by reading parsed instructions and account-level balance changes together.
- Power Solana explorers, support tooling, and post-mortem workflows for user-reported transaction issues.
How to Use 🛠️
- Pass the Solana transaction signature in
signature. - Read
signers,slot,fee, andcompute_units_consumedfirst for a quick execution summary. - Use
sol_balance_changesandtoken_balance_changesto understand fund movement across accounts. - Inspect
instructions,inner_instructions, andlogswhen you need protocol-level execution detail.
Best Practices ✅
- Store signatures and slots together in your own systems so follow-up lookups stay deterministic.
- Use this endpoint alongside account detail when you need both transaction traces and final account state.
- Expect deeply nested objects on complex DeFi transactions and parse them lazily where possible.
Limitations ⚠️
- Solana only.