ots_getTransactionBySenderAndNonce | Hyperliquid EVM

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

POST /evm

ots_getTransactionBySenderAndNonce

cURL

curl --request POST \
  --url https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274/evm \
  --header 'Content-Type: application/json' \
  --data '
{
  "jsonrpc": "2.0",
  "method": "ots_getTransactionBySenderAndNonce",
  "params": [
    "0x5555555555555555555555555555555555555555",
    0
  ],
  "id": 1
}
'

200

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "hash": "0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381",
    "nonce": "0x0",
    "from": "0x5555555555555555555555555555555555555555"
  }
}

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 for the full availability breakdown.

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.

Get your own node endpoint today

Start for free and get your app to production levels immediately. No credit card required.

You can sign up with your GitHub, X, Google, or Microsoft account.

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

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
  }'

Use your own endpoint in your code. The code examples use a placeholder Chainstack endpoint (YOUR_CHAINSTACK_ENDPOINT) — replace it with your own Hyperliquid node endpoint from the Chainstack console. The curl above uses a shared public endpoint for quick checks only; do not use it in production.

Example response (transaction found)

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381"
}

Example response (not found)

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": null
}

Finding multiple transactions

To find a sequence of transactions from an address:

// 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.

Body

application/json

jsonrpc · enum<string> · default: 2.0 · required

JSON-RPC version

Available options: 2.0

method · enum<string> · default: ots_getTransactionBySenderAndNonce · required

The RPC method name

Available options: ots_getTransactionBySenderAndNonce

params · array · required

Parameters: [sender address, nonce]

id · integer · default: 1 · required

Request identifier

Response

200 - application/json

Successful response with transaction data

jsonrpc · string

JSON-RPC version

id · integer

Request identifier

result · object

Transaction object or null if not found