Transaction

A transaction is the execution of an endpoint on the Hedera network. The vast majority of these will be CRYPTO_TRANSFERs. Some more examples: calling a function on a contract (CONTRACT_CALL); creating an account (CRYPTO_CREATE); and, deleting a file (FILE_DELETE).

Field	Description
`id`	The Transaction ID that was generated on the client at the time of submission to the network. This is formatted as `{operator}@{validStart.seconds}.{validStart.nanos}` which is used in the Hedera SDKs as the serialization format for `TransactionId`.
`validStartAt`	The timestamp from when the transaction can be processed. This is used by Hedera as a check to make sure clients and nodes have a closely synchronized clock.
`hash`	The unique hash of this transaction. Multiple transactions with the same ID may be submitted (note that only one will actually succeed) and thus this is the preferred way of identifying a transaction.
`operator`	The account ID ( `{shard}.{realm}.{account}` ) of the account that is charged the fees for the transaction. Hedera itself (in the protobufs) name this only "account" however the SDKs define this as the "operator".
`node`	The node ID ( `{shard}.{realm}.{account}` ) that this transaction was submitted to.
`type`	The type of the transaction (ex., `CRYPTO_CREATE`, `CRYPTO_UPDATE`, `FILE_DELETE`, `CRYPTO_TRANSFER`, ...)
`consensusAt`	The timestamp when the network reached consensus on this transaction. This is the point when the receipt becomes available.
`value`	The total value (in tinybar) that is being transferred. This does not include the fee or any internal transfers (from a contract call).
`fee`	The fee (in tinybar) that was charged to the `operator`.
`memo`	The (max 100-byte) memo that was included with the transaction.
`status`	The status of the transaction. `SUCCESS` means success. All other values are failures (indicating the transfers did not actually occur, but the fee is still charged).
`entity`	The relevant entity (file/account/contract) in this transaction. For example, this will be the contract ID that was created; the file ID that was deleted; or, the account ID that is being updated.
`transfers[]`

{
  "id": "[email protected]",
  "validStartAt": "2020-01-20T06:16:29.120842903Z",
  "hash": "eb7cec093e78533afcfa596e1d30c1056972bebdcd96210d5fe1b2dcbaf7571f1514d417ec6022889b76ea59ec838fb0",
  "operator": "0.0.19783",
  "node": "0.0.8",
  "type": "CRYPTO_TRANSFER",
  "consensusAt": "2020-01-20T06:16:39.454240Z",
  "value": 90000,
  "fee": 411476,
  "memo": null,
  "status": "SUCCESS",
  "entity": null,
  "transfers": [
    {
      "account": "0.0.14698",
      "amount": -90000,
      "type": "value"
    },
    {
      "account": "0.0.14684",
      "amount": 90000,
      "type": "value"
    },
    {
      "account": "0.0.98",
      "amount": 2640,
      "type": "fee"
    },
    {
      "account": "0.0.19783",
      "amount": -2640,
      "type": "fee"
    },
    {
      "account": "0.0.98",
      "amount": 403439,
      "type": "fee"
    },
    {
      "account": "0.0.8",
      "amount": 5397,
      "type": "fee"
    },
    {
      "account": "0.0.19783",
      "amount": -408836,
      "type": "fee"
    }
  ]
}