Transaction Details
Tx hash
d8455cc2b9e4ebd6e8cfd06e4b9d6a6a1eff4256b2007522fc618fa3aabc6604
Tx prefix hash
ed4e13bced4b64a8e97a6ed9cf24bb13fbd6c18a7f35ebd8e6fc3a8d1f2f0863
Tx public key
484df7d4980e6a4f9ebe2b71c7a39b5f88b0e45d2189d0c06a3071830717a0f2
Age [y:d:h:m:s]
05:161:12:18:44
Timestamp [UCT] (epoch)
2019-06-22 10:12:02 (1561198322)
Block
203994 (1396864 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01484df7d4980e6a4f9ebe2b71c7a39b5f88b0e45d2189d0c06a3071830717a0f20211000000b81f899f85000000000000000000032100445743e3574e4d663f75825fe77995dcf39ed193aa0c5fc5da2b57d703807c7f
Outputs
1 output(s) for total of 18.387195652 ARQ
stealth address amount amount idx
00: d28c2394446d8a5d0f2f83b81b81d05eb67f6740dd61e9ccbf6995cd8a6c2d7b 18.387195652 930653 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": 204012, 
  "vin": [ {
      "gen": {
        "height": 203994
      }
    }
  ], 
  "vout": [ {
      "amount": 18387195652, 
      "target": {
        "key": "d28c2394446d8a5d0f2f83b81b81d05eb67f6740dd61e9ccbf6995cd8a6c2d7b"
      }
    }
  ], 
  "extra": [ 1, 72, 77, 247, 212, 152, 14, 106, 79, 158, 190, 43, 113, 199, 163, 155, 95, 136, 176, 228, 93, 33, 137, 208, 192, 106, 48, 113, 131, 7, 23, 160, 242, 2, 17, 0, 0, 0, 184, 31, 137, 159, 133, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 68, 87, 67, 227, 87, 78, 77, 102, 63, 117, 130, 95, 231, 121, 149, 220, 243, 158, 209, 147, 170, 12, 95, 197, 218, 43, 87, 215, 3, 128, 124, 127
  ], 
  "rct_signatures": {
    "type": 0
  }
}