How to view pending transactions in Phantom? (Queue status)

Accessing Transaction Queue in Phantom Wallet

1. Open the Phantom browser extension or mobile application and ensure it is unlocked with your active wallet.

2. Navigate to the account dashboard where your token balances and recent activity are displayed.

3. Tap or click the three-dot menu icon located in the top-right corner of the interface.

4. Select “Transaction History” from the dropdown or modal options.

5. Toggle the filter option labeled “Pending Only” to isolate unconfirmed transactions.

Understanding Pending vs. Queued State

1. A transaction appears as pending when it has been signed, broadcast to the Solana network, and awaits inclusion in a block.

2. Phantom itself does not maintain an internal queue like Ethereum’s txpool; instead, it reflects the state reported by connected RPC endpoints.

3. If a transaction remains pending beyond typical confirmation time, it may be stuck due to low priority fee or network congestion.

4. Transactions with insufficient compute budget or failed signature verification never enter a pending state—they fail immediately upon submission.

5. Phantom displays no explicit “queue” for unsubmitted transactions; unsigned or draft transactions reside only in local memory until explicitly sent.

RPC-Level Visibility Limitations

1. Phantom relies on Solana’s JSON-RPC API methods such as getSignatureStatuses to fetch real-time status of known signatures.

2. It cannot retrieve transactions that have not yet been submitted to the cluster—even if constructed locally—because they lack a signature hash.

3. No native method exists within Phantom’s UI to inspect mempool contents or view transactions submitted by other wallets.

4. The wallet does not cache or replay unsigned payloads; once dismissed, drafts are discarded without persistence.

5. Custom RPC providers configured in Phantom settings influence visibility—some may delay status updates or omit failed entries.

Manual Verification via Explorer

1. Copy the transaction signature shown beside each pending entry in Phantom’s history panel.

2. Paste it into a Solana blockchain explorer such as explorer.solana.com or xnfts.xyz.

3. Observe fields including “Finalized”, “Confirmed”, or “Dropped” to determine current disposition.

4. If the explorer returns “Not found”, the transaction was either never broadcast or pruned from validator memory after timeout.

5. For transactions with custom instructions or CPI calls, verify instruction-level outcomes using the “Instructions” tab in the explorer.

Frequently Asked Questions

Q: Can Phantom show transactions that are signed but not yet broadcast?A: No. Phantom only displays transactions after they have been submitted to the network and assigned a signature.

Q: Why does a transaction stay “pending” for over two minutes on Solana?A: This usually indicates a priority fee too low to compete during peak load, or an instruction failure masked by optimistic confirmation reporting.

Q: Does Phantom support canceling a pending transaction?A: Solana does not support transaction cancellation. Users must wait for timeout or replace it with a new transaction sharing the same address and higher priority fee.

Q: How many pending transactions can Phantom track simultaneously?A: Phantom imposes no hard limit—it displays all signatures returned by the configured RPC endpoint, up to the maximum batch size supported by that provider.