Transaction Details
Tx hash
9a59b1c6bc38e89125e173ce5dc7a79cb5c4188be9d6b77b8e055bb12174c4b3
Tx prefix hash
71cd41d019e04972076503b7f2bb566cc1a595f3e54e307488e8660f92b080a3
Tx public key
522988b4633e1ac9c686cf738081c2b2a5930fd7357c672e7a6fd1e8e0d4e5c1
Age [y:d:h:m:s]
05:168:08:30:35
Timestamp [UCT] (epoch)
2019-06-11 16:14:52 (1560269692)
Block
196350 (1401757 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01522988b4633e1ac9c686cf738081c2b2a5930fd7357c672e7a6fd1e8e0d4e5c10321000767f0cf11e9d9d3174706a359335eebd8e909be261a7df826edd052088c21be021b000000000000000000000000000b1eb72600000000000000000000
Outputs
1 output(s) for total of 18.454338244 ARQ
stealth address amount amount idx
00: 807ec76cd2891c1cbe7e49d2f3d7faf4d6cad61bf211a00e20c5128eb875efae 18.454338244 887581 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": 196368, 
  "vin": [ {
      "gen": {
        "height": 196350
      }
    }
  ], 
  "vout": [ {
      "amount": 18454338244, 
      "target": {
        "key": "807ec76cd2891c1cbe7e49d2f3d7faf4d6cad61bf211a00e20c5128eb875efae"
      }
    }
  ], 
  "extra": [ 1, 82, 41, 136, 180, 99, 62, 26, 201, 198, 134, 207, 115, 128, 129, 194, 178, 165, 147, 15, 215, 53, 124, 103, 46, 122, 111, 209, 232, 224, 212, 229, 193, 3, 33, 0, 7, 103, 240, 207, 17, 233, 217, 211, 23, 71, 6, 163, 89, 51, 94, 235, 216, 233, 9, 190, 38, 26, 125, 248, 38, 237, 208, 82, 8, 140, 33, 190, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 30, 183, 38, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}