Transaction Details
Tx hash
5a2fecbe0782c1a06c1127b1e716b7e952a027adffa15f07b9dfa14fdc4066bc
Tx prefix hash
e88d2c1441829d43e23c99c3cf3c4c247333e5e3ea29d95d4c0646ad2df1dc8f
Tx public key
47911879acdefa9c9b1b352e802966ef0a15653afd7404c84a05218d7c51b91f
Age [y:d:h:m:s]
05:143:17:15:43
Timestamp [UCT] (epoch)
2019-07-09 17:41:44 (1562694104)
Block
216444 (1384084 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
0147911879acdefa9c9b1b352e802966ef0a15653afd7404c84a05218d7c51b91f0211000000fa091d2b5c00000000000000000003210049cfea69df8d0f5034aceec93ef5f01766afc7df7c8acb5e78bafd2958cf7d0d
Outputs
1 output(s) for total of 18.278427039 ARQ
stealth address amount amount idx
00: b57e00cdcb1c0c0e72ea3b2bbf89d8b0aafe5cc607d3f1f54423b49c4a494b1c 18.278427039 1004551 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": 216462, 
  "vin": [ {
      "gen": {
        "height": 216444
      }
    }
  ], 
  "vout": [ {
      "amount": 18278427039, 
      "target": {
        "key": "b57e00cdcb1c0c0e72ea3b2bbf89d8b0aafe5cc607d3f1f54423b49c4a494b1c"
      }
    }
  ], 
  "extra": [ 1, 71, 145, 24, 121, 172, 222, 250, 156, 155, 27, 53, 46, 128, 41, 102, 239, 10, 21, 101, 58, 253, 116, 4, 200, 74, 5, 33, 141, 124, 81, 185, 31, 2, 17, 0, 0, 0, 250, 9, 29, 43, 92, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 73, 207, 234, 105, 223, 141, 15, 80, 52, 172, 238, 201, 62, 245, 240, 23, 102, 175, 199, 223, 124, 138, 203, 94, 120, 186, 253, 41, 88, 207, 125, 13
  ], 
  "rct_signatures": {
    "type": 0
  }
}