How to see pending transactions in Phantom? (Queue Management)

Accessing the Transaction Queue

1. Open the Phantom wallet extension or mobile application and ensure you are logged into your active account.

2. Navigate to the wallet’s main interface where your token balances and recent activity are displayed.

3. Locate and tap or click the icon representing pending operations—this is typically a clock-shaped indicator or a small badge showing a number next to “Activity” or “History”.

4. Select “Pending” or “Queue” from the filter options at the top of the transaction list view.

5. The system will render all unconfirmed transactions grouped by network, including Solana, Ethereum, or EVM-compatible chains supported by Phantom.

Understanding Transaction Status Indicators

1. Each entry in the queue displays a status label such as “Sending”, “Waiting for Confirmation”, or “Dropped”.

2. A green checkmark appears only after finality; until then, the status remains visually distinct with an animated pulse or yellow warning border.

3. Transaction hashes are fully visible and clickable, allowing users to copy them directly for external verification on blockchain explorers.

4. Estimated confirmation time is shown when available—this value depends on current network congestion and fee priority settings.

5. Phantom does not display raw mempool data but instead relies on RPC node feedback to infer whether a transaction is still propagating or has been rejected by validators.

Modifying or Cancelling Pending Transactions

1. For Ethereum-based networks, users may replace a pending transaction using the “Speed Up” or “Cancel” buttons adjacent to the relevant item.

2. Clicking “Speed Up” opens a modal where gas price and limit can be adjusted before broadcasting a new version with higher priority.

3. Selecting “Cancel” constructs a zero-value transfer to self with elevated gas, effectively invalidating the original submission.

4. On Solana, cancellation is not natively supported due to the absence of replaceable nonces—pending instructions remain immutable once signed and submitted.

5. Users attempting to override Solana transactions must wait for timeout or failure, then resubmit with updated parameters like compute budget or priority fees.

Monitoring Network Conditions

1. Phantom integrates real-time RPC responses to assess cluster health, displaying alerts if nodes report high latency or inconsistent state.

2. Fee estimation logic adjusts dynamically based on recent block velocities and validator vote patterns across the selected chain.

3. Users can manually switch between default and custom RPC endpoints under Settings > Network Preferences to improve queue responsiveness.

4. During periods of elevated load, Phantom may throttle automatic queue refreshes to prevent UI freezing or duplicate submissions.

5. Historical confirmation durations are not stored locally but inferred from live RPC metrics during each session.

Frequently Asked Questions

Q: Why does Phantom show “Pending” even after several minutes on Solana?Because Solana uses deterministic block times and leader rotation, some transactions experience variable inclusion windows—especially during epoch transitions or validator outages.

Q: Can I view pending transactions from multiple wallets simultaneously in one Phantom instance?No. Phantom isolates queues per connected account; switching accounts resets the displayed pending list without merging states.

Q: Does Phantom store unsigned transactions in its queue?No. Only cryptographically signed payloads submitted to the network appear in the pending section; drafts or unsent requests remain in local memory until confirmed.

Q: Are queued transactions encrypted while stored in Phantom’s interface?Yes. All pending entries reside exclusively in the browser’s secure context or device memory and never persist beyond the active session unless exported manually by the user.