Transactions API

Whether a transaction succeeded, on ETH/BNB/BASE/STABLE/SOL

Whether one transaction succeeded and, when it failed, a human-readable reason — the narrow, cheap question, on five of the six chains the full transaction lookup serves.

GET/api/external/transaction-analysis/transaction-status/{chain}/{hash}

What it returns

Whether the transaction succeeded, and a human-readable failure reason when it did not and one exists. Served on ETH, BNB, BASE, STABLE and SOL; every other chain returns 400. The transaction endpoint serves all five of these too and answers the same question and more (who sent it, which tokens moved, a decoded failure reason), so the two are a cost choice rather than a coverage split: prefer that one when you want any of the rest, and this one when the outcome is all you need. Where both answer they agree on the outcome, and that was measured per chain rather than assumed. status is null when nothing could be established — on SOL, also for a signature no transaction is known by and for one not yet confirmed by the cluster. revertReason is null for a successful transaction AND for a failed one with no resolvable reason — never confuse the two, read status for outcome. On SOL the reason names the failing instruction, e.g. "Instruction 3: custom program error: 0x3".

Chains

  • Solana SOL
  • BNB Chain BNB
  • Ethereum ETH
  • Stable STABLE
  • Base BASE

Request

Send your key in the x-dex-data-key header. Replace each <placeholder> with a real value.

curl -H "x-dex-data-key: $DEXDATA_API_KEY" \
  "https://api.dexdata.io/api/external/transaction-analysis/transaction-status/SOL/<hash>"
Parameters
ParameterDescription
chain

path · string · required

ETH, BNB, BASE, STABLE and SOL; every other chain returns 400. The transaction endpoint now serves all five of these and answers the same question and more, so the two differ by cost rather than by coverage — this is the cheap path when the outcome is all you need.
hash

path · string · required

The transaction: a 0x-prefixed 64-hex-character hash on ETH, BNB, BASE and STABLE; the transaction's first signature, base58, on SOL.

Response fields

A JSON response. Every field is always present; null means the value could not be established, never zero.

Response fields of Whether a transaction succeeded, on ETH/BNB/BASE/STABLE/SOL
FieldTypeDescription
statusstring | nullWhether the transaction succeeded. null when this could not be established. Never "success" for a hash that was never mined on the four EVM chains — that is a 404.
revertReasonstring | nullHuman-readable failure reason, e.g. "execution reverted", or on SOL "Instruction 3: custom program error: 0x3". null on a successful transaction and on a failed one with no resolvable reason — never inferred, never a placeholder for success.

Start building with DexData today

Sign in, create a key and make your first call in a minute. Free credits every month, and you only pay for calls that succeed.

Get a free API key