Get live transaction status

GET/v1/transactions/{txid}/status

TSCScan API v1.0.0 · Transactions · also at /api/v1/mainnet/transactions/{txid}/status

Indexed confirmed transactions reuse compact inclusion metadata for at most 300 seconds within configured cache budgets; confirmations are derived from the latest verified indexed checkpoint identified by optional X-Chain-Height/X-Chain-Hash headers. After a rollback, reuse requires the inclusion height to survive every intervening bounded rollback fence; fork suffixes, missing/pruned history, rebuild gaps, restart/routing changes and unhealthy probes revoke reuse. Read-only requests may wait within the configured original-request recovery grace; mutations are never retried. An indexed miss falls back to live Core mempool then confirmed txindex without waiting for indexing; Core results omit indexed chain headers and are cached at most 500 ms. Core failure, blocks behind known headers, initial block download or unsynchronized txindex returns 503, never false not_found.

Example

curl 'https://api.tensorcash.org/v1/transactions/edf886b19fe4bc2e9d2bd2cc690836d569984acc0dca1592c606f93978841e9f/status'

Parameters

NameInTypeRequiredDescription
txidpathstringYesExact 64-character hexadecimal transaction ID.

Responses

StatusDescriptionBody
200Successful read from one Indexer snapshot
400Invalid argument or page conditions
401Authentication required
403Permission denied
404Absent in a ready indexed range
409Verified chain continuity invalidation
422Bounded response would exceed byte budget
429Quota exceeded; Retry-After supplied
503Data or eligible source not ready
504Bounded upstream query timed out

Schemas

TransactionStateResponse

FieldTypeRequiredDescription
dataTransactionStateYesOperation result.

TransactionState

FieldTypeRequiredDescription
txidstringYesQueried transaction identifier.
state"pending" | "confirmed" | "not_found"YesConfirmed inclusion at a verified indexed checkpoint, or live Core observation for unindexed/pending/unknown transactions. not_found requires synchronized Core txindex and does not prove the transaction never existed.
confirmationsintegerYesConfirmations at X-Chain-Height when indexed chain headers are present; otherwise the live Core observation. Zero if pending/not found. Indexed counts never use an unverified observed Core height.
blockobject | nullYesConfirmed block. Null when unavailable.
mempool_timeinteger | nullYesCore mempool entry time in Unix seconds. Null when unavailable.
observed_at_unixintegerYesStatus projection/observation time in Unix seconds. Core observations may be reused for at most 500 ms; indexed confirmation counts are derived from the current verified checkpoint.

Problem

FieldTypeRequiredDescription
typestringYesProblem type URI; about:blank is used for the current error family.
titlestringYesShort human-readable problem title, normally the stable error code.
statusintegerYesHTTP status code for this problem response.
code"INVALID_ARGUMENT" | "UNAUTHORIZED" | "FORBIDDEN" | "RESOURCE_NOT_FOUND" | "CHAIN_ANCHOR_INVALIDATED" | "RATE_LIMITED" | "DATA_NOT_READY" | "SERVICE_UNAVAILABLE" | "UPSTREAM_TIMEOUT" | "RESPONSE_TOO_LARGE" | "CORE_UNAVAILABLE" | "CORE_METHOD_UNAVAILABLE" | "CORE_DATA_NOT_READY" | "CORE_CAPACITY" | "TRANSACTION_CAPACITY" | "TRANSACTION_STATE_CHANGED" | "TRANSACTION_REJECTED" | "BROADCAST_OUTCOME_UNKNOWN" | "UNSUPPORTED_ASSET_POLICY"YesStable machine-readable error code; use this instead of matching message text.
request_idstringYesIdentifier also supplied in X-Request-ID; include it when reporting an error.
detailstring—Human-readable explanation of the error.
retry_after_secondsinteger—Suggested wait in seconds before retrying; where present, agrees with Retry-After.
Source
TSCScan public API v1.0.0 (12f98c5) · rHuhu · MIT