Transaction Details
Tx hash
e0d9eafab514a975a7ad8509410a7f51c6c9f3cb8e4466cb4d4a351ddac649ab
Tx prefix hash
fd3dec056b2bfbc3297ae7c765deb4a00e8e530a5073e4fddd224fa15ad7b053
Tx public key
5fd46dae81a5b2ed56c5df8d3d65dc50f3f785f4390ab10b9780582252f7ca15
Age [y:d:h:m:s]
05:298:19:15:49
Timestamp [UCT] (epoch)
2019-02-01 11:17:39 (1549019859)
Block
103452 (1494824 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
015fd46dae81a5b2ed56c5df8d3d65dc50f3f785f4390ab10b9780582252f7ca15032100683ce7fe13a574d51d5b46e7e6b877e04f6c3ee19d7bb5cfbdb4af73306e4a8a021b0000000000000000000000000005e59e0d00000000000000000000
Outputs
1 output(s) for total of 19.290189614 ARQ
stealth address amount amount idx
00: 593165b77852cc44e006a31cf79617b3445833c8f5f36cd80f39e41a2a7c0ff3 19.290189614 511223 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": 103470, 
  "vin": [ {
      "gen": {
        "height": 103452
      }
    }
  ], 
  "vout": [ {
      "amount": 19290189614, 
      "target": {
        "key": "593165b77852cc44e006a31cf79617b3445833c8f5f36cd80f39e41a2a7c0ff3"
      }
    }
  ], 
  "extra": [ 1, 95, 212, 109, 174, 129, 165, 178, 237, 86, 197, 223, 141, 61, 101, 220, 80, 243, 247, 133, 244, 57, 10, 177, 11, 151, 128, 88, 34, 82, 247, 202, 21, 3, 33, 0, 104, 60, 231, 254, 19, 165, 116, 213, 29, 91, 70, 231, 230, 184, 119, 224, 79, 108, 62, 225, 157, 123, 181, 207, 189, 180, 175, 115, 48, 110, 74, 138, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 229, 158, 13, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}