Skip to main content
GET
Transaction details

Authorizations

X-Api-Key
string
header
required

API key (programmatic access — recommended)

Send your API key in the X-Api-Key header. Keys start with nxs_ and are created in the dashboard (or via POST /api/keys with a session JWT).

Each key is scoped to one chain and one network (for example cardano-mainnet), fixed at creation time. It cannot query a different network on the same chain, and it cannot query a different chain at all. A mismatched network parameter returns 400 Network Mismatch. Create one key per chain and network under the same account.

This is the credential most integrations should use.

Path Parameters

txHash
string
required
Required string length: 1 - 128
Pattern: ^[a-fA-F0-9]+$

Query Parameters

network
enum<string>
Available options:
CARDANO_MAINNET,
CARDANO_PREPROD,
CARDANO_PREVIEW,
APEX_PRIME_MAINNET,
APEX_VECTOR_MAINNET,
APEX_VECTOR_TESTNET,
MIDNIGHT_MAINNET,
MIDNIGHT_PREPROD,
MIDNIGHT_PREVIEW,
BITCOIN_MAINNET,
BITCOIN_TESTNET4

Response

OK

txHash
string
block_hash
string
block_height
integer<int64>
absolute_slot
integer<int64>
txTimestamp
integer<int64>
txSize
integer<int32>
total_output
string
fee
string
deposit
string
invalid_before
string
invalid_after
string
reference_inputs
object[]
inputs
object[]
outputs
object[]
withdrawals
object[]
assets_minted
object[]
metadata
any
certificates
object[]
native_scripts
object[]
plutus_contracts
object[]
block_epoch
integer<int64>
{key}
any