Transaction Details
Tx hash
72aeff784211c64e7320da73afb0a8d834e4d9442890fbd6962deea82dc92df2
Tx prefix hash
9a10de23565b54bad5f4119618e49411ba673bac7939347e5f0d2a88b425faf6
Tx public key
02902943f46628f0566c6ed1dff1126bcf80c804afd0ed89c3be6a63310bbf87
Age [y:d:h:m:s]
05:316:05:42:17
Timestamp [UCT] (epoch)
2019-01-14 23:12:11 (1547507531)
Block
90935 (1507292 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1367 kB
Tx version
2
RingCT type
0
Extra
0102902943f46628f0566c6ed1dff1126bcf80c804afd0ed89c3be6a63310bbf87032107484e8fd650630fdefa32a85a0d51bfe8df986351b8788d58920e75cc445127e902140000002504e19d00000000000000000000000000
Outputs
1 output(s) for total of 19.405777562 ARQ
stealth address amount amount idx
00: ac9ef5bc59f402d8f03f7956da973e0a3df0e4df5df1fb239fd6386c2ed25cc0 19.405777562 448996 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": 90953, 
  "vin": [ {
      "gen": {
        "height": 90935
      }
    }
  ], 
  "vout": [ {
      "amount": 19405777562, 
      "target": {
        "key": "ac9ef5bc59f402d8f03f7956da973e0a3df0e4df5df1fb239fd6386c2ed25cc0"
      }
    }
  ], 
  "extra": [ 1, 2, 144, 41, 67, 244, 102, 40, 240, 86, 108, 110, 209, 223, 241, 18, 107, 207, 128, 200, 4, 175, 208, 237, 137, 195, 190, 106, 99, 49, 11, 191, 135, 3, 33, 7, 72, 78, 143, 214, 80, 99, 15, 222, 250, 50, 168, 90, 13, 81, 191, 232, 223, 152, 99, 81, 184, 120, 141, 88, 146, 14, 117, 204, 68, 81, 39, 233, 2, 20, 0, 0, 0, 37, 4, 225, 157, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}