Transaction Details
Tx hash
1f2ae7e0cd859ca5168a47d5a4e02a14158c26a13f16662ec3e626255e947fb8
Tx prefix hash
25ee277e2a00bb0caffd3ccb9d6086c687f9355bc2b8953221d4a838508f882f
Tx public key
d314a5f2e4a65e5fdf0b843e4e88b16cdf3f3cfcd4b00b33b7c8b34e243562e0
Age [y:d:h:m:s]
05:309:16:25:25
Timestamp [UCT] (epoch)
2019-01-14 20:14:03 (1547496843)
Block
90849 (1502623 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
01d314a5f2e4a65e5fdf0b843e4e88b16cdf3f3cfcd4b00b33b7c8b34e243562e00321005c3d48d5d4eca809fefb985aa102a5ddef310d036c56c881e90854be29a0b07c02100000000f3e3f02000000000000000000
Outputs
1 output(s) for total of 19.406464586 ARQ
stealth address amount amount idx
00: 0582a56f4ad001775993284d3b60b34f624c93d4f64fa67b6ebbf1834b4b9368 19.406464586 448580 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": 90867, 
  "vin": [ {
      "gen": {
        "height": 90849
      }
    }
  ], 
  "vout": [ {
      "amount": 19406464586, 
      "target": {
        "key": "0582a56f4ad001775993284d3b60b34f624c93d4f64fa67b6ebbf1834b4b9368"
      }
    }
  ], 
  "extra": [ 1, 211, 20, 165, 242, 228, 166, 94, 95, 223, 11, 132, 62, 78, 136, 177, 108, 223, 63, 60, 252, 212, 176, 11, 51, 183, 200, 179, 78, 36, 53, 98, 224, 3, 33, 0, 92, 61, 72, 213, 212, 236, 168, 9, 254, 251, 152, 90, 161, 2, 165, 221, 239, 49, 13, 3, 108, 86, 200, 129, 233, 8, 84, 190, 41, 160, 176, 124, 2, 16, 0, 0, 0, 15, 62, 63, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}