> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ots_getTransactionBySenderAndNonce | Hyperliquid EVM

> Reference docs for the ots_getTransactionBySenderAndNonce JSON-RPC method on the Hyperliquid EVM blockchain, available via Chainstack JSON-RPC nodes.

<Info>
  This method is available on Chainstack. Not all Hyperliquid methods are available on Chainstack, as the open-source node implementation does not support them yet — see [Hyperliquid methods](/docs/hyperliquid-methods) for the full availability breakdown.
</Info>

The `ots_getTransactionBySenderAndNonce` JSON-RPC method retrieves a transaction hash by specifying the sender address and nonce on the Hyperliquid EVM blockchain. This Otterscan-specific method helps locate transactions when you know the sender and nonce but not the transaction hash.

<Check>
  **Get your own node endpoint today**

  [Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.

  You can sign up with your GitHub, X, Google, or Microsoft account.
</Check>

## Parameters

1. **sender address** (string, required): The address that sent the transaction
2. **nonce** (integer, required): The nonce value used for the transaction

## Response

The method returns the transaction hash if found, or null if no transaction exists with the specified sender and nonce.

### Response structure

* `result` — the transaction hash (32-byte hex string), or `null` if not found

## Usage example

```shell Shell theme={"system"}
curl -X POST https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "method": "ots_getTransactionBySenderAndNonce",
    "params": ["0x5555555555555555555555555555555555555555", 0],
    "id": 1
  }'
```

### Example response (transaction found)

```json theme={"system"}
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381"
}
```

### Example response (not found)

```json theme={"system"}
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": null
}
```

### Finding multiple transactions

To find a sequence of transactions from an address:

```javascript theme={"system"}
// Find transactions with nonces 0 through 5
for (let nonce = 0; nonce <= 5; nonce++) {
  const params = ["0x5555555555555555555555555555555555555555", nonce];
  // Make RPC call with params
}
```

## Use cases

The `ots_getTransactionBySenderAndNonce` method is essential for:

* **Transaction recovery**: Find lost transaction hashes using sender and nonce
* **Wallet debugging**: Track down specific transactions from an account
* **Nonce management**: Verify which nonces have been used by an address
* **Transaction replacement**: Find original transactions before replacement
* **Account auditing**: Systematically review all transactions from an address
* **Support tools**: Help users find their transactions without the hash
* **Forensic analysis**: Track transaction sequences from specific accounts
* **Testing verification**: Confirm test transactions were submitted
* **MEV analysis**: Study transaction ordering and nonce patterns
* **Integration recovery**: Recover from lost transaction tracking in dApps

This method is particularly useful when debugging wallet issues or when transaction hashes weren't properly stored by an application.


## OpenAPI

````yaml /openapi/hyperliquid_node_api/evm_ots_get_transaction_by_sender_and_nonce.json post /evm
openapi: 3.0.0
info:
  title: Hyperliquid EVM API - ots_getTransactionBySenderAndNonce
  version: 1.0.0
servers:
  - url: >-
      https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274
security: []
paths:
  /evm:
    post:
      summary: ots_getTransactionBySenderAndNonce
      description: >-
        Find a transaction by sender address and nonce on Hyperliquid EVM.
        Useful for tracking specific account transactions.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - jsonrpc
                - method
                - params
                - id
              properties:
                jsonrpc:
                  type: string
                  enum:
                    - '2.0'
                  default: '2.0'
                  description: JSON-RPC version
                method:
                  type: string
                  enum:
                    - ots_getTransactionBySenderAndNonce
                  default: ots_getTransactionBySenderAndNonce
                  description: The RPC method name
                params:
                  type: array
                  description: 'Parameters: [sender address, nonce]'
                  default:
                    - '0x5555555555555555555555555555555555555555'
                    - 0
                id:
                  type: integer
                  default: 1
                  description: Request identifier
            example:
              jsonrpc: '2.0'
              method: ots_getTransactionBySenderAndNonce
              params:
                - '0x5555555555555555555555555555555555555555'
                - 0
              id: 1
      responses:
        '200':
          description: Successful response with transaction data
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                    description: JSON-RPC version
                  id:
                    type: integer
                    description: Request identifier
                  result:
                    type: object
                    description: Transaction object or null if not found
              example:
                jsonrpc: '2.0'
                id: 1
                result:
                  hash: >-
                    0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381
                  nonce: '0x0'
                  from: '0x5555555555555555555555555555555555555555'

````