---
title: "List latest transactions"
method: GET
path: "/v1/chains/{chainId}/transactions"
tags: ["EVM Transactions"]
---

# List latest transactions

`GET /v1/chains/{chainId}/transactions`

Lists the latest transactions. Filterable by status.

## Path parameters

- `chainId` string, required

## Query parameters

- `pageToken` string
- `pageSize` integer
- `status` 'failed' | 'success'

## Response `200`

Successful response

- ListNativeTransactionsResponse
  - `nextPageToken` string — A token, which can be sent as `pageToken` to retrieve the next page. If this field is omitted or empty, there are no subsequent pages.
  - `transactions` NativeTransaction[], required
    - `blockNumber` string, required — The block number on the chain.
    - `blockTimestamp` number, required — The block creation (proposal) timestamp in seconds
    - `blockTimestampMilliseconds` number — The block creation (proposal) timestamp in milliseconds. Available only after Granite upgrade.
    - `blockMinDelayExcess` number — Minimum block delay in milliseconds. Available only after Granite upgrade.
    - `blockHash` string, required — The block hash identifier.
    - `chainId` string, required — The EVM chain ID on which the transaction occured.
    - `blockIndex` number, required — The index at which the transaction occured in the block (0-indexed).
    - `txHash` string, required — The transaction hash identifier.
    - `txStatus` string, required — The transaction status, which is either 0 (failed) or 1 (successful).
    - `txType` number, required — The transaction type.
    - `gasLimit` string, required — The gas limit set for the transaction.
    - `gasUsed` string, required — The amount of gas used.
    - `gasPrice` string, required — The gas price denominated by the number of decimals of the native token.
    - `nonce` string, required — The nonce used by the sender of the transaction.
    - `from` RichAddress, required
      - `name` string — The contract name.
      - `symbol` string — The contract symbol.
      - `decimals` number — The number of decimals the token uses. For example `6`, means to divide the token amount by `1000000` to get its user representation.
      - `logoUri` string — The logo uri for the address.
      - `address` string, required — A wallet or contract address in mixed-case checksum encoding.
    - `to` RichAddress, required
      - `name` string — The contract name.
      - `symbol` string — The contract symbol.
      - `decimals` number — The number of decimals the token uses. For example `6`, means to divide the token amount by `1000000` to get its user representation.
      - `logoUri` string — The logo uri for the address.
      - `address` string, required — A wallet or contract address in mixed-case checksum encoding.
    - `method` Method
      - `callType` 'NATIVE_TRANSFER' | 'CONTRACT_CALL' | 'CONTRACT_CREATION', required — The contract call type. NATIVE_TRANSFER indicates a transfer of the native token without any smart-contract interaction. CONTRACT_CALL indicates a smart-contract interaction. CONTRACT_CREATION indicates a smart-contract creation.
      - `methodHash` string, required — The contract method hash identifier. The method hash is only set if the `callType` is `CONTRACT_CALL`.
      - `methodName` string — The contract method name including parameter types. If the `callType` is `NATIVE_TRANSFER` this is set to 'Native Transfer'. If the `callType` is `CONTRACT_CREATION` this is set to 'Contract Created'.
    - `value` string, required

## Other responses

- `400` — Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error.
- `401` — When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401.
- `403` — When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403.
- `404` — The error is mostly returned when the client requests with either mistyped URL, or the passed resource is moved or deleted, or the resource doesn't exist.
- `429` — This error is returned when the client has sent too many, and has hit the rate limit.
- `500` — The error is a generic server side error that is returned for any uncaught and unexpected issues on the server side. This should be very rare, and you may reach out to us if the problem persists for a longer duration.
- `502` — This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server.
- `503` — The error is returned for certain routes on a particular Subnet. This indicates an internal problem with our Subnet node, and may not necessarily mean the Subnet is down or affected.

---

[API](https://skmtc.net/avax/apis/data-api.md) · [All operations](https://skmtc.net/avax/apis/data-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/avax/data-api/versions/745a94fa47f5/schema)