Transaction Details
Tx hash
a6a2e1db4a0b37bb7bb4e76d8a33fdfd18f4337e25366f63261e9ad1b00a9e28
Tx prefix hash
5d051f1ffc2630a21fa745b85957c6ff71cb8cd002afbc878bbcb1b225ecd7af
Tx public key
9650e6c25dafbf7583e22f07c02f3e1bfa95c57c0f6929cc58f20e54dfb7cb8a
Age [y:d:h:m:s]
05:193:09:14:18
Timestamp [UCT] (epoch)
2019-05-17 17:25:09 (1558113909)
Block
178525 (1419634 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
019650e6c25dafbf7583e22f07c02f3e1bfa95c57c0f6929cc58f20e54dfb7cb8a03210072e42dee3c0a95999d3df11d8ffe8b0238b35edbc2f802dc4111189a6399ae22021b000000000000000000000000002901d3b100000000000000000000
Outputs
1 output(s) for total of 18.611861683 ARQ
stealth address amount amount idx
00: 1a3790953a8eea06e37caf76c680f3529c88c24fe0ffc173e3aa76c9ec5e1ff8 18.611861683 805873 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": 178543, 
  "vin": [ {
      "gen": {
        "height": 178525
      }
    }
  ], 
  "vout": [ {
      "amount": 18611861683, 
      "target": {
        "key": "1a3790953a8eea06e37caf76c680f3529c88c24fe0ffc173e3aa76c9ec5e1ff8"
      }
    }
  ], 
  "extra": [ 1, 150, 80, 230, 194, 93, 175, 191, 117, 131, 226, 47, 7, 192, 47, 62, 27, 250, 149, 197, 124, 15, 105, 41, 204, 88, 242, 14, 84, 223, 183, 203, 138, 3, 33, 0, 114, 228, 45, 238, 60, 10, 149, 153, 157, 61, 241, 29, 143, 254, 139, 2, 56, 179, 94, 219, 194, 248, 2, 220, 65, 17, 24, 154, 99, 153, 174, 34, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 41, 1, 211, 177, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}