How to View Your Wallet's Transaction History in Rabby Wallet

Accessing Transaction History

1. Open the Rabby Wallet browser extension and unlock it using your password or hardware wallet.

2. Click on the account icon located in the top-right corner of the interface.

3. Select the specific blockchain network where you want to review activity—Rabby supports 96 EVM-compatible chains, so ensure correct chain selection before proceeding.

4. Scroll down to locate the Transaction History section directly beneath your balance display.

5. Tap or click on any individual transaction to expand detailed metadata including block number, timestamp, status, gas used, and input data hash.

Filtering and Sorting Options

1. Use the dropdown menu labeled “All Networks” to isolate transactions from a single chain such as Ethereum, BSC, or Arbitrum.

2. Toggle between “Incoming”, “Outgoing”, and “All” to narrow results based on directionality of value flow.

3. Apply date range filters by clicking the calendar icon and selecting start and end dates manually.

4. Sort entries chronologically by clicking the “Time” column header—ascending or descending order is applied instantly.

5. Search for specific token transfers or contract interactions using the search bar; entering a contract address or transaction hash yields exact matches.

Exporting Raw Data

1. Locate the three-dot menu icon next to the “Transaction History” title.

2. Choose “Export Transactions” from the contextual options.

3. Select CSV format for spreadsheet compatibility or JSON for developer tool ingestion.

4. Confirm export initiation—the file will download automatically without requiring external authentication.

5. Verify integrity by cross-referencing exported timestamps and transaction hashes with Etherscan or equivalent explorers for that chain.

Understanding Status Indicators

1. A green checkmark signifies confirmed and irreversible execution on-chain.

2. A yellow clock icon indicates pending state—transaction has been broadcast but not yet included in a block.

3. A red exclamation mark reflects failure due to revert, out-of-gas, or invalid signature conditions.

4. Grayed-out entries denote internal wallet operations like balance updates or approval resets—not actual on-chain events.

5. Hovering over any status badge reveals tooltip explanations sourced directly from Rabby’s internal RPC response parsing logic.

Common Questions and Answers

Q: Can I view transactions from wallets imported via private key?A: Yes. Rabby treats all imported accounts—including those restored via private key—as first-class entities with full transaction history visibility across supported networks.

Q: Why do some transactions appear duplicated across multiple chains?A: This occurs when identical contract addresses exist on different EVM chains—for example, USDT deployed on both Ethereum and Tron—and Rabby displays them separately per active network context.

Q: Is there a limit to how far back transaction history loads?A: No fixed limit exists. History retrieval depends entirely on node endpoint responsiveness and archival depth of the connected RPC provider—not on Rabby’s local storage constraints.

Q: Does Rabby store my transaction data on its servers?A: No. All transaction queries are executed client-side against public RPC endpoints. Rabby does not retain, log, or transmit historical records to any remote infrastructure.