Transaction Details
Tx hash
8e55c722d38d74309cf96685f3911a3caff2dfb1d393d95f92af5c810a3f3e7c
Tx prefix hash
bd3639edef4f8552e52f4addb3ee89a97a290deb3faa7abf05fe23bae7670237
Tx public key
136d0e681f03841d3e15077698ee8bc5692010e26d35cccdefe355e8737eeaec
Age [y:d:h:m:s]
05:221:23:20:38
Timestamp [UCT] (epoch)
2019-04-19 14:27:49 (1555684069)
Block
158361 (1440130 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01136d0e681f03841d3e15077698ee8bc5692010e26d35cccdefe355e8737eeaec03210041f709541c49b4f1f80deea4d35037d376146bdbd92967e327523fce725b777f021b00000000000000000000000000479c3e8400000000000000000000
Outputs
1 output(s) for total of 18.791676814 ARQ
stealth address amount amount idx
00: 9fa919664e7c9ec1ae3b153e5518332995b96b7c529d3c07c42a749a7ce1b914 18.791676814 726197 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": 158379, 
  "vin": [ {
      "gen": {
        "height": 158361
      }
    }
  ], 
  "vout": [ {
      "amount": 18791676814, 
      "target": {
        "key": "9fa919664e7c9ec1ae3b153e5518332995b96b7c529d3c07c42a749a7ce1b914"
      }
    }
  ], 
  "extra": [ 1, 19, 109, 14, 104, 31, 3, 132, 29, 62, 21, 7, 118, 152, 238, 139, 197, 105, 32, 16, 226, 109, 53, 204, 205, 239, 227, 85, 232, 115, 126, 234, 236, 3, 33, 0, 65, 247, 9, 84, 28, 73, 180, 241, 248, 13, 238, 164, 211, 80, 55, 211, 118, 20, 107, 219, 217, 41, 103, 227, 39, 82, 63, 206, 114, 91, 119, 127, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 71, 156, 62, 132, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}