Transaction Details
Tx hash
a4398228431a06d403a1144c3941c72205088e6942fe3e12f9b4fa2c77f675db
Tx prefix hash
e415808cf2aa984102498d8c581ac526ca844713e22787b45d81d2dd9df3327e
Tx public key
4e5a70b204f4e5a08260671a2589c2d53c8ed10955746f7a83a4aab605b53595
Age [y:d:h:m:s]
05:320:05:26:43
Timestamp [UCT] (epoch)
2019-01-14 22:21:44 (1547504504)
Block
90912 (1510105 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014e5a70b204f4e5a08260671a2589c2d53c8ed10955746f7a83a4aab605b535950321002421e84591f20b01ba81d461e88652e57dfa7842f84e0935bb24bb11a3c0323c021b000000000000000000000000000f11dca400000000000000000000
Outputs
1 output(s) for total of 19.406114710 ARQ
stealth address amount amount idx
00: aaaceff35b3b1c06607a99d26f18ce0b634e09e7b5c743bafacaf61f57533095 19.406114710 448868 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": 90930, 
  "vin": [ {
      "gen": {
        "height": 90912
      }
    }
  ], 
  "vout": [ {
      "amount": 19406114710, 
      "target": {
        "key": "aaaceff35b3b1c06607a99d26f18ce0b634e09e7b5c743bafacaf61f57533095"
      }
    }
  ], 
  "extra": [ 1, 78, 90, 112, 178, 4, 244, 229, 160, 130, 96, 103, 26, 37, 137, 194, 213, 60, 142, 209, 9, 85, 116, 111, 122, 131, 164, 170, 182, 5, 181, 53, 149, 3, 33, 0, 36, 33, 232, 69, 145, 242, 11, 1, 186, 129, 212, 97, 232, 134, 82, 229, 125, 250, 120, 66, 248, 78, 9, 53, 187, 36, 187, 17, 163, 192, 50, 60, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 15, 17, 220, 164, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}