Transaction Details
Tx hash
f0d4d8df3141924bb0dc5a6dbf4e6f7e832d1fb1db79064608ffec8cb9bf61f1
Tx prefix hash
574bcaa731f79b8b05e92e67e11ce013d0ffe20c6bd8c5a768cb2bccc53c8455
Tx public key
1f4ab47fdf6eb7b510c5205dc9dd1edad6b57fe4e9b0a2f657cb4a6053a22d5e
Age [y:d:h:m:s]
05:237:02:30:25
Timestamp [UCT] (epoch)
2019-04-03 19:09:02 (1554318542)
Block
147174 (1450824 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
011f4ab47fdf6eb7b510c5205dc9dd1edad6b57fe4e9b0a2f657cb4a6053a22d5e032100ae869e0ef9004a77d423cc6abd3ca7cc41511197fc0a425806f9d92d61be1c69021b0000000000000000000000000035567a2e00000000000000000000
Outputs
1 output(s) for total of 18.892186572 ARQ
stealth address amount amount idx
00: e78b4a293c60d5beea1681bd6e0a39ca1cfaa627ef2bc2161605acc62a5136a8 18.892186572 675770 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": 147192, 
  "vin": [ {
      "gen": {
        "height": 147174
      }
    }
  ], 
  "vout": [ {
      "amount": 18892186572, 
      "target": {
        "key": "e78b4a293c60d5beea1681bd6e0a39ca1cfaa627ef2bc2161605acc62a5136a8"
      }
    }
  ], 
  "extra": [ 1, 31, 74, 180, 127, 223, 110, 183, 181, 16, 197, 32, 93, 201, 221, 30, 218, 214, 181, 127, 228, 233, 176, 162, 246, 87, 203, 74, 96, 83, 162, 45, 94, 3, 33, 0, 174, 134, 158, 14, 249, 0, 74, 119, 212, 35, 204, 106, 189, 60, 167, 204, 65, 81, 17, 151, 252, 10, 66, 88, 6, 249, 217, 45, 97, 190, 28, 105, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 53, 86, 122, 46, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}