Transaction Details
Tx hash
e01ba9dca03a07769f9eb4a38eeea8e6ba75ed9dae74a9f3a0f898650b59bae4
Tx prefix hash
ed1ae24802f13b16b7b4cb1b8fe78d78bc5cebcc3c5fc375f559294ecf6e82b9
Tx public key
e6d43d580a42d8d802a2cf2e6bb1b8b43f5d15fb70e78867ccb86814c67c488b
Age [y:d:h:m:s]
05:088:02:38:06
Timestamp [UCT] (epoch)
2019-07-11 03:49:22 (1562816962)
Block
217454 (1344828 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e6d43d580a42d8d802a2cf2e6bb1b8b43f5d15fb70e78867ccb86814c67c488b032100a538ba55e1905e6a4a12c40650e5d65c3380b1a0b073d86ef5dae38bce7fb173021b0000000000000000000000000092c4c81900000000000000000000
Outputs
1 output(s) for total of 18.269560316 ARQ
stealth address amount amount idx
00: ece56e14bcf00a0b875c8946b9aa0229503bb4ddf6f19ffd2793cd507f3d1a67 18.269560316 1009988 of 0

Check which outputs belong to given ARQ address/subaddress and viewkey
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side

Prove to someone that you have sent them ARQ in this transaction
Tx private key can be obtained using get_tx_key command in arqma-wallet-cli
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side

        
          {
  "version": 2, 
  "unlock_time": 217472, 
  "vin": [ {
      "gen": {
        "height": 217454
      }
    }
  ], 
  "vout": [ {
      "amount": 18269560316, 
      "target": {
        "key": "ece56e14bcf00a0b875c8946b9aa0229503bb4ddf6f19ffd2793cd507f3d1a67"
      }
    }
  ], 
  "extra": [ 1, 230, 212, 61, 88, 10, 66, 216, 216, 2, 162, 207, 46, 107, 177, 184, 180, 63, 93, 21, 251, 112, 231, 136, 103, 204, 184, 104, 20, 198, 124, 72, 139, 3, 33, 0, 165, 56, 186, 85, 225, 144, 94, 106, 74, 18, 196, 6, 80, 229, 214, 92, 51, 128, 177, 160, 176, 115, 216, 110, 245, 218, 227, 139, 206, 127, 177, 115, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 146, 196, 200, 25, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}