Transaction Operations
resource: transaction — look up a transaction's status and fee
get
| Field | Type | Required | Description |
|---|---|---|---|
transactionId | text | ✓ Yes | Accepts either native or dash form (see below) |
network | select | No | See Networks. |
Accepted Transaction ID Formats
| Form | Example |
|---|---|
| Native | [email protected] |
| Dash | 0.0.1-1690000000-000000000 |
Both refer to the same transaction — the payer account ID, the transaction's start timestamp seconds, and nanoseconds. Use whichever form your upstream system already produces; the node normalizes either.
Example response:
{
"transactionId": "[email protected]",
"status": "SUCCESS",
"result": "SUCCESS",
"consensusTimestamp": "1690000003.123456789",
"chargedFeeTinybars": 91780
}| Response Field | Meaning |
|---|---|
status / result | Hedera's response code, e.g. SUCCESS, INVALID_SIGNATURE, INSUFFICIENT_ACCOUNT_BALANCE. |
consensusTimestamp | When the network reached consensus on this transaction — this is its permanent, immutable timestamp. |
chargedFeeTinybars | The actual network fee charged, in tinybar. Divide by 100,000,000 for HBAR (see Utility Operations). |
Eventual consistency: The Mirror Node can lag live consensus by a few seconds. A
transaction you just submitted may briefly return "not found" from
transaction.get —
see Troubleshooting for a retry pattern.