Transaction Details
Tx hash
43f62b4eeef56e0538abc1c4b48af181d9b6d3d5a1b87c657959f93674ae1089
Tx prefix hash
b2a576f2ced4bf2a5586b2fc2273c2ecfdf2793cc0f35e6ac19722c4e30e291d
Tx public key
2a291a72b61dc90921a1a80d6b3a27c2db4681559bc526988ebd6d66b840b3ed
Age [y:d:h:m:s]
05:315:17:35:08
Timestamp [UCT] (epoch)
2019-01-15 16:55:20 (1547571320)
Block
91477 (1506919 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
012a291a72b61dc90921a1a80d6b3a27c2db4681559bc526988ebd6d66b840b3ed032100bdd8fe2f11ee8675e5248dfa5a0b36ed2606395e504cd198530d70c2ecb9b55b021b0000000000000000000000000024734c3b00000000000000000000
Outputs
1 output(s) for total of 19.400654116 ARQ
stealth address amount amount idx
00: f61f2ca55f0c79652e1686a37f8230ae5b9c190f8e14c30e5d1be1261aa75819 19.400654116 451325 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": 91495, 
  "vin": [ {
      "gen": {
        "height": 91477
      }
    }
  ], 
  "vout": [ {
      "amount": 19400654116, 
      "target": {
        "key": "f61f2ca55f0c79652e1686a37f8230ae5b9c190f8e14c30e5d1be1261aa75819"
      }
    }
  ], 
  "extra": [ 1, 42, 41, 26, 114, 182, 29, 201, 9, 33, 161, 168, 13, 107, 58, 39, 194, 219, 70, 129, 85, 155, 197, 38, 152, 142, 189, 109, 102, 184, 64, 179, 237, 3, 33, 0, 189, 216, 254, 47, 17, 238, 134, 117, 229, 36, 141, 250, 90, 11, 54, 237, 38, 6, 57, 94, 80, 76, 209, 152, 83, 13, 112, 194, 236, 185, 181, 91, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 36, 115, 76, 59, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}