> ## 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_getInternalOperations | Hyperliquid EVM

> Reference docs for the ots_getInternalOperations 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_getInternalOperations` JSON-RPC method retrieves all internal ETH transfers and operations that occurred within a transaction on the Hyperliquid EVM blockchain. This Otterscan-specific method reveals value transfers that happen inside smart contract execution, which are not visible in standard transaction receipts.

## Parameters

1. **transaction hash** (string, required): The hash of the transaction to analyze

## Response

The method returns an array of internal operation objects representing all value transfers within the transaction.

### Response structure

Each internal operation contains:

* `type` — the operation type (0: transfer, 1: self-destruct, 2: create, 3: create2)
* `from` — the address sending the value
* `to` — the address receiving the value
* `value` — the amount of ETH transferred in wei (hex)

## Usage example

<CodeGroup>
  ```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_getInternalOperations",
      "params": ["0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381"],
      "id": 1
    }'
  ```

  ```python web3.py theme={"system"}
  from web3 import Web3

  w3 = Web3(Web3.HTTPProvider("YOUR_CHAINSTACK_ENDPOINT"))

  tx_hash = "0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381"

  # ots_getInternalOperations is an Otterscan method, so call it via the raw JSON-RPC provider
  response = w3.provider.make_request("ots_getInternalOperations", [tx_hash])
  print(response["result"])
  ```

  ```javascript ethers.js theme={"system"}
  import { JsonRpcProvider } from "ethers";

  const provider = new JsonRpcProvider("YOUR_CHAINSTACK_ENDPOINT");

  const txHash =
    "0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381";

  // ots_getInternalOperations is an Otterscan method, so send a raw JSON-RPC request
  const operations = await provider.send("ots_getInternalOperations", [txHash]);
  console.log(operations);
  ```

  ```typescript viem theme={"system"}
  import { createPublicClient, http } from "viem";

  const client = createPublicClient({
    transport: http("YOUR_CHAINSTACK_ENDPOINT"),
  });

  const txHash =
    "0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381";

  // ots_getInternalOperations is an Otterscan method, so use the raw request method
  const operations = await client.request({
    method: "ots_getInternalOperations" as any,
    params: [txHash] as any,
  });
  console.log(operations);
  ```
</CodeGroup>

<Note>
  **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](https://console.chainstack.com/). The curl above uses a shared public endpoint for quick checks only; do not use it in production.
</Note>

### Example response

```json theme={"system"}
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": [
    {
      "type": 0,
      "from": "0x5555555555555555555555555555555555555555",
      "to": "0x6666666666666666666666666666666666666666",
      "value": "0xde0b6b3a7640000"
    },
    {
      "type": 0,
      "from": "0x6666666666666666666666666666666666666666",
      "to": "0x7777777777777777777777777777777777777777",
      "value": "0x6f05b59d3b20000"
    }
  ]
}
```

### Operation types

The `type` field indicates the operation:

* `0` — Regular ETH transfer
* `1` — Self-destruct (contract deletion with balance transfer)
* `2` — Contract creation via CREATE opcode
* `3` — Contract creation via CREATE2 opcode

## Use cases

The `ots_getInternalOperations` method is essential for:

* **Value flow analysis**: Track how ETH moves through complex contract interactions
* **DeFi debugging**: Understand token swaps and liquidity operations
* **Security auditing**: Detect unexpected value transfers in contracts
* **Payment splitting**: Analyze how contracts distribute payments
* **Fee tracking**: Monitor protocol fees and revenue sharing
* **MEV analysis**: Study arbitrage and sandwich attack patterns
* **Wallet tracking**: Follow funds through mixer and privacy protocols
* **Tax reporting**: Identify all value transfers for accounting
* **Contract verification**: Ensure contracts handle ETH as expected
* **Forensic analysis**: Investigate exploits and fund movements

This method is particularly valuable for understanding complex DeFi transactions where multiple contracts interact and transfer value in ways not visible through standard transaction data.


## OpenAPI

````yaml openapi/hyperliquid_node_api/hyperevm/evm_ots_get_internal_operations.json post /evm
openapi: 3.0.0
info:
  title: Hyperliquid EVM API - ots_getInternalOperations
  version: 1.0.0
servers:
  - url: >-
      https://hyperliquid-mainnet.core.chainstack.com/4f8d8f4040bdacd1577bff8058438274
security: []
paths:
  /evm:
    post:
      summary: ots_getInternalOperations
      description: >-
        Get internal ETH transfers and operations within a transaction on
        Hyperliquid EVM. Track value movements through contract interactions.
      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_getInternalOperations
                  default: ots_getInternalOperations
                  description: The RPC method name
                params:
                  type: array
                  description: 'Parameters: [transaction hash]'
                  default:
                    - >-
                      0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381
                id:
                  type: integer
                  default: 1
                  description: Request identifier
            example:
              jsonrpc: '2.0'
              method: ots_getInternalOperations
              params:
                - >-
                  0xf94f3d2ed5b59aefb6a0e566af8e86552014d84f6ed2f38a1366dedffe723381
              id: 1
      responses:
        '200':
          description: Successful response with internal operations
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                    description: JSON-RPC version
                  id:
                    type: integer
                    description: Request identifier
                  result:
                    type: array
                    description: Array of internal operations
              example:
                jsonrpc: '2.0'
                id: 1
                result:
                  - type: 0
                    from: '0x5555555555555555555555555555555555555555'
                    to: '0x6666666666666666666666666666666666666666'
                    value: '0xde0b6b3a7640000'

````