Transaction Details
Tx hash
85d008d058338bdf7a17048c7bb6312a5dfd9a3d2f9b6d37c0868c5e41bb83d3
Tx prefix hash
53e209fccb7bcb3791efde97e078cd6de6d36fd771895e37afc4b0c4e403bccc
Tx public key
4ec7973e6e1141c2c927f8a626e2226ba218dad4a2c9d1c2c01d0ca02c472611
Age [y:d:h:m:s]
05:325:02:50:33
Timestamp [UCT] (epoch)
2019-01-05 17:02:21 (1546707741)
Block
84370 (1513579 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014ec7973e6e1141c2c927f8a626e2226ba218dad4a2c9d1c2c01d0ca02c472611032100368b95a4b7d699eab6d92bd31ec30c0d368701c2e876a930003430bba40266fd021b00000000000000000000000000046098fe00000000000000000000
Outputs
1 output(s) for total of 19.466512183 ARQ
stealth address amount amount idx
00: e38237c7b84e2168d6032e2b1f1c15dd873fe4dfee462f1536147b81e4c7c9e6 19.466512183 417918 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": 84388, 
  "vin": [ {
      "gen": {
        "height": 84370
      }
    }
  ], 
  "vout": [ {
      "amount": 19466512183, 
      "target": {
        "key": "e38237c7b84e2168d6032e2b1f1c15dd873fe4dfee462f1536147b81e4c7c9e6"
      }
    }
  ], 
  "extra": [ 1, 78, 199, 151, 62, 110, 17, 65, 194, 201, 39, 248, 166, 38, 226, 34, 107, 162, 24, 218, 212, 162, 201, 209, 194, 192, 29, 12, 160, 44, 71, 38, 17, 3, 33, 0, 54, 139, 149, 164, 183, 214, 153, 234, 182, 217, 43, 211, 30, 195, 12, 13, 54, 135, 1, 194, 232, 118, 169, 48, 0, 52, 48, 187, 164, 2, 102, 253, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 96, 152, 254, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}