Transaction Details
Tx hash
64aefe33d95b3e242f2c9c4de220ffffa2d7ddeaeb4977a796b4425a22031c3e
Tx prefix hash
eef5146f9ab401d1308e7d543032cc483ba28daa673781e024dfcec50dc03238
Tx public key
289aea60044374f41052881e91f07fd8b0cf198108a5f95d799ae9d5fa395e16
Age [y:d:h:m:s]
05:269:12:44:38
Timestamp [UCT] (epoch)
2019-01-11 23:48:50 (1547250530)
Block
88809 (1474364 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01289aea60044374f41052881e91f07fd8b0cf198108a5f95d799ae9d5fa395e16032100d548e36fd99617945a3164112169acb72b2f10e198e69a20e00f848a4764a1a6021b000000000000000000000000001736d44000000000000000000000
Outputs
1 output(s) for total of 19.425397991 ARQ
stealth address amount amount idx
00: 47c78595d4976fa9fd7400727e9df985ff41c682e5eef1270141551925f4b6e6 19.425397991 439161 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": 88827, 
  "vin": [ {
      "gen": {
        "height": 88809
      }
    }
  ], 
  "vout": [ {
      "amount": 19425397991, 
      "target": {
        "key": "47c78595d4976fa9fd7400727e9df985ff41c682e5eef1270141551925f4b6e6"
      }
    }
  ], 
  "extra": [ 1, 40, 154, 234, 96, 4, 67, 116, 244, 16, 82, 136, 30, 145, 240, 127, 216, 176, 207, 25, 129, 8, 165, 249, 93, 121, 154, 233, 213, 250, 57, 94, 22, 3, 33, 0, 213, 72, 227, 111, 217, 150, 23, 148, 90, 49, 100, 17, 33, 105, 172, 183, 43, 47, 16, 225, 152, 230, 154, 32, 224, 15, 132, 138, 71, 100, 161, 166, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 23, 54, 212, 64, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}