List latest transactions

get

https://glacier-api.avax.network/v1/networks/{network}/blockchains/{blockchainId}/transactions

Lists the latest transactions on one of the Primary Network chains.

Transactions are filterable by addresses, txTypes, and timestamps. When querying for latest transactions without an address parameter, filtering by txTypes and timestamps is not supported. An address filter must be provided to utilize txTypes and timestamp filters.

Given that each transaction may return a large number of UTXO objects, bounded only by the maximum transaction size, the query may return less transactions than the provided page size. The result will contain less results than the page size if the number of utxos contained in the resulting transactions reach a performance threshold.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

blockchainId

string

enum

required

A primary network blockchain id or alias.

network

string

enum

required

Either mainnet or a testnet.

Allowed:

Query Params

addresses

string

required

A comma separated list of X-Chain or P-Chain wallet addresses, starting with "avax"/"fuji", "P-avax"/"P-fuji" or "X-avax"/"X-fuji". Also accepts EVM formatted addresses starting with "0x" for C-Chain-related atomic transaction lookups.

txTypes

array of objects

Query param for filtering items based on transaction types.

txTypes

startTimestamp

integer

≥ 0

Query param for retrieving items after a specific timestamp.

endTimestamp

integer

≥ 0

Query param for retrieving items before a specific timestamp.

pageToken

string

A page token, received from a previous list call. Provide this to retrieve the subsequent page.

pageSize

integer

1 to 100

Defaults to 10

The maximum number of items to return. The minimum page size is 1. The maximum pageSize is 100.

sortOrder

string

enum

The order by which to sort results. Use "asc" for ascending order, "desc" for descending order. Sorted by timestamp or the sortBy query parameter, if provided.

Allowed:

Responses

Language

Credentials

Header

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Successful response

400Bad requests generally mean the client has passed invalid or malformed parameters. Error messages in the response could help in evaluating the error.

401When a client attempts to access resources that require authorization credentials but the client lacks proper authentication in the request, the server responds with 401.

403When a client attempts to access resources with valid credentials but doesn't have the privilege to perform that action, the server responds with 403.

404The 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.

429This error is returned when the client has sent too many, and has hit the rate limit.

500The 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.

502This is an internal error indicating invalid response received by the client-facing proxy or gateway from the upstream server.

503The 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.