Transaction Details
Tx hash
51d116e1dca86caf00d3f9c1cad778ab69120c96a8cd5a9cdae257ec06048fe5
Tx prefix hash
867188d0cee655321c00c264c4382733f5e2151b968e18579779c9e34bd414a6
Tx public key
8d830397126a21e582d5b0da7557b6ca05d598b935141b7403cc6cf84f459fd0
Age [y:d:h:m:s]
05:230:00:17:34
Timestamp [UCT] (epoch)
2019-04-14 18:06:53 (1555265213)
Block
154923 (1445828 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
018d830397126a21e582d5b0da7557b6ca05d598b935141b7403cc6cf84f459fd003210083cdff874e3170102896581f0d68ef63bbdccbf42035f980498f9df3e50fef08021b000000000000000000000000002a68aeda00000000000000000000
Outputs
1 output(s) for total of 18.822508525 ARQ
stealth address amount amount idx
00: 4aabf8c75a09753cbe8d1567bad9d5364c8546547c5401a51d4b1a4f2aa60698 18.822508525 709167 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": 154941, 
  "vin": [ {
      "gen": {
        "height": 154923
      }
    }
  ], 
  "vout": [ {
      "amount": 18822508525, 
      "target": {
        "key": "4aabf8c75a09753cbe8d1567bad9d5364c8546547c5401a51d4b1a4f2aa60698"
      }
    }
  ], 
  "extra": [ 1, 141, 131, 3, 151, 18, 106, 33, 229, 130, 213, 176, 218, 117, 87, 182, 202, 5, 213, 152, 185, 53, 20, 27, 116, 3, 204, 108, 248, 79, 69, 159, 208, 3, 33, 0, 131, 205, 255, 135, 78, 49, 112, 16, 40, 150, 88, 31, 13, 104, 239, 99, 187, 220, 203, 244, 32, 53, 249, 128, 73, 143, 157, 243, 229, 15, 239, 8, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 42, 104, 174, 218, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}