Transaction Details
Tx hash
c2ae33dc70cf3cd71ce2798aefbd4e63f6f59c28e2014363e5e83fb556c9fbc9
Tx prefix hash
a1d5c5f546d2f743a93695d3e6d58a51b038b7edc3e778a7fe479bafd0c06309
Tx public key
0d06da1797e99c40dfe5b4e89704d55b6b3c1e876bbf22a90aa56b14d3a8a6df
Age [y:d:h:m:s]
05:262:18:30:29
Timestamp [UCT] (epoch)
2019-03-15 09:56:58 (1552643818)
Block
133406 (1469011 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010d06da1797e99c40dfe5b4e89704d55b6b3c1e876bbf22a90aa56b14d3a8a6df0321001fc8285d6fe985ef9bf1525e768647477e2bca045f9009c44e58d340d7df647a021b000000000000000000000000005eaf984d00000000000000000000
Outputs
1 output(s) for total of 19.016623605 ARQ
stealth address amount amount idx
00: 7c07bc462cbaf7ba539856d480feb09ed43b9e310afbe3185c6fd240b1780351 19.016623605 628678 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": 133424, 
  "vin": [ {
      "gen": {
        "height": 133406
      }
    }
  ], 
  "vout": [ {
      "amount": 19016623605, 
      "target": {
        "key": "7c07bc462cbaf7ba539856d480feb09ed43b9e310afbe3185c6fd240b1780351"
      }
    }
  ], 
  "extra": [ 1, 13, 6, 218, 23, 151, 233, 156, 64, 223, 229, 180, 232, 151, 4, 213, 91, 107, 60, 30, 135, 107, 191, 34, 169, 10, 165, 107, 20, 211, 168, 166, 223, 3, 33, 0, 31, 200, 40, 93, 111, 233, 133, 239, 155, 241, 82, 94, 118, 134, 71, 71, 126, 43, 202, 4, 95, 144, 9, 196, 78, 88, 211, 64, 215, 223, 100, 122, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 94, 175, 152, 77, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}