---
title: "Get last activity timestamp by addresses v2"
method: POST
path: "/v1/networks/{network}/blockchains/{blockchainId}/lastActivityTimestampByAddresses"
tags: ["Primary Network UTXOs"]
---

# Get last activity timestamp by addresses v2

`POST /v1/networks/{network}/blockchains/{blockchainId}/lastActivityTimestampByAddresses`

Gets the last activity timestamp for the supplied addresses on one of the Primary Network chains. V2 route supports querying for more addresses.

## Path parameters

- `blockchainId` '11111111111111111111111111111111LpoYY' | '2oYMBNV4eNHyqk2fjjV5nVQLDbtmNJzq5s3qs3Lo6ftnC6FByM' | '2JVSBoinj9C2J33VntvzYtVJNZdN2NKiwwKjcumHUWEb5DbBrm' | '2q9e4r6Mu3U68nU1fYjgbR6JvwrRx36CohpAX5UQxse55x1Q5' | 'yH8D7ThNJkxmtkuv2jgBa4P1Rn3Qpr4pPr7QYNfcdoS6k6HWp' | 'p-chain' | 'x-chain' | 'c-chain', required
- `network` 'mainnet' | 'fuji' | 'testnet', required

## Request body

- PrimaryNetworkAddressesBodyDto
  - `addresses` string, required — Comma-separated list of primary network addresses

## Response `200`

Successful response

- LastActivityTimestamp
  - `timestamp` number, required — Unix timestamp in seconds at which the last activity occurred.
  - `blockNumber` string, required — Block height at which the last activity occurred.
  - `txHash` string, required — Transaction hash of the transaction that created or consumed the address' UTXOs.
  - `utxoId` string, required — UTXO ID of the UTXO that was created or consumed.
  - `isConsumed` boolean, required — Whether the last activity was a consumption of an existing UTXO.
  - `chainName` 'p-chain' | 'x-chain' | 'c-chain', required
  - `network` 'mainnet' | 'fuji', 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.dev/avax/apis/data-api.md) · [All operations](https://skmtc.dev/avax/apis/data-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/avax/data-api/revisions/86448a21e2b1/schema)