Solana / transaction
Solana transaction lookup
Look up any Solana transaction on Solscan. tx.taxi detects the format, picks the right Solana explorer, and redirects.
Solana uses base58-encoded Ed25519 public keys for account addresses and base58 signatures for transactions, so its identifiers look nothing like an EVM 0x value. tx.taxi's configured primary Solana explorer is Solscan, widely used for SPL token inspection, program accounts, and instruction decoding. Paste a Solana address, a transaction signature, or a slot number at tx.taxi/{value} and the router classifies the base58 format, picks Solscan, and 302-redirects to the matching /account/, /tx/, or /block/ page. Wallets and bots can call the same classifier via /api/v1/resolve. On this page: Solana transaction lookups specifically.
How it works
- Copy your
Solana transaction(e.g. the transaction hash from your wallet). - Paste into the search above or visit
tx.taxi/<your-transaction>directly. - tx.taxi detects the Solana format and redirects to Solscan.
Live transactions
Frequently asked questions
What does a Solana address look like?
Solana addresses are base58-encoded 32-byte public keys, usually 32-44 characters long. They use the bitcoin base58 alphabet (no 0, O, I, l) and have no prefix. tx.taxi detects them and routes to Solscan.
How long is a Solana transaction signature?
A Solana transaction signature is a 64-byte Ed25519 signature, encoded as base58 it runs roughly 87-88 characters. It is what you paste to look up a tx on Solscan.
Are Solana accounts the same as wallets?
Not quite. Every wallet is an account, but Solana accounts also include token accounts, program accounts, and PDAs. Solscan's account page shows the type, owner program, and on-chain data for any account you paste.