Transaction Details
Tx hash
313d2ce7ff425b7f85f6652f412a3b281f44338e86622a5dd9fc442c91effa83
Tx prefix hash
d276454c37ea88b1be4ce2ad4e59e798043e2aac14b3092dfb36265d416a0511
Tx public key
c8a272d25d1f21c7c3c830c984d1439e9a1cdc7bab9598ff8e998662c83e7ed4
Age [y:d:h:m:s]
05:178:15:28:00
Timestamp [UCT] (epoch)
2019-06-04 20:59:28 (1559681968)
Block
191484 (1409090 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01c8a272d25d1f21c7c3c830c984d1439e9a1cdc7bab9598ff8e998662c83e7ed403210080ef3d540e3db6a3ecf60c8c6d5ffea3bc89f8f84f5032c245771f63a86a847c021b0000000000000000000000000007f0dc9c00000000000000000000
Outputs
1 output(s) for total of 18.497207378 ARQ
stealth address amount amount idx
00: b05a19567255736656d01cf7e8c69a8a7124d97fd96cbb88ba32bc1fe12e286c 18.497207378 863294 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": 191502, 
  "vin": [ {
      "gen": {
        "height": 191484
      }
    }
  ], 
  "vout": [ {
      "amount": 18497207378, 
      "target": {
        "key": "b05a19567255736656d01cf7e8c69a8a7124d97fd96cbb88ba32bc1fe12e286c"
      }
    }
  ], 
  "extra": [ 1, 200, 162, 114, 210, 93, 31, 33, 199, 195, 200, 48, 201, 132, 209, 67, 158, 154, 28, 220, 123, 171, 149, 152, 255, 142, 153, 134, 98, 200, 62, 126, 212, 3, 33, 0, 128, 239, 61, 84, 14, 61, 182, 163, 236, 246, 12, 140, 109, 95, 254, 163, 188, 137, 248, 248, 79, 80, 50, 194, 69, 119, 31, 99, 168, 106, 132, 124, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 240, 220, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}