Transaction Details
Tx hash
ed05d71b17507143a3db9d19445145d46c7109fcdc5bd853db211f97f6129b04
Tx prefix hash
9d705062a3c0157d25db633424b82c1d245b80e15f7ff69d9550224279ad357c
Tx public key
e57564358e2b055ade9d1aaccf7e1d46ff004bf6d19995f88a2481f846847989
Age [y:d:h:m:s]
05:177:19:38:07
Timestamp [UCT] (epoch)
2019-06-05 04:07:35 (1559707655)
Block
191700 (1408497 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e57564358e2b055ade9d1aaccf7e1d46ff004bf6d19995f88a2481f84684798903210023b3e72acf36dfb52b7d8b0d1af8e582c15938417b5061a172ce04c191efe1d2021b0000000000000000000000000031eeb05f00000000000000000000
Outputs
1 output(s) for total of 18.495302322 ARQ
stealth address amount amount idx
00: ae909adaa4e055b5184b10a96939982a44f877d069cd42cba610dbdac45b8f44 18.495302322 864385 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": 191718, 
  "vin": [ {
      "gen": {
        "height": 191700
      }
    }
  ], 
  "vout": [ {
      "amount": 18495302322, 
      "target": {
        "key": "ae909adaa4e055b5184b10a96939982a44f877d069cd42cba610dbdac45b8f44"
      }
    }
  ], 
  "extra": [ 1, 229, 117, 100, 53, 142, 43, 5, 90, 222, 157, 26, 172, 207, 126, 29, 70, 255, 0, 75, 246, 209, 153, 149, 248, 138, 36, 129, 248, 70, 132, 121, 137, 3, 33, 0, 35, 179, 231, 42, 207, 54, 223, 181, 43, 125, 139, 13, 26, 248, 229, 130, 193, 89, 56, 65, 123, 80, 97, 161, 114, 206, 4, 193, 145, 239, 225, 210, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 49, 238, 176, 95, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}