Transaction Details
Tx hash
0e2b08747b2c6f787b39ba82d1e429c5e74d78f934e6eaef5abc19a55a43ab55
Tx prefix hash
a0e44d304b72c8076d0719da2851c68ade291c1cb8838f2cc5af680a10c4d69f
Tx public key
aa2f7a3e0865be880fbf94e34c8b2e79d3fb4222c3fe66335f60c83af0e2a979
Age [y:d:h:m:s]
05:195:12:07:47
Timestamp [UCT] (epoch)
2019-03-27 01:25:42 (1553649942)
Block
141696 (1421511 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01aa2f7a3e0865be880fbf94e34c8b2e79d3fb4222c3fe66335f60c83af0e2a9790321004c1dc51ae03ac14a95b2d2f6c8bf46da222d6d5f35250ebe55d027d343296e14021b000000000000000000000000000a30e6f300000000000000000000
Outputs
1 output(s) for total of 18.941599636 ARQ
stealth address amount amount idx
00: cbfdf920549b463ab4cf5b5d5874c90c99cf149c407a3019c44ad97573fee313 18.941599636 653102 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": 141714, 
  "vin": [ {
      "gen": {
        "height": 141696
      }
    }
  ], 
  "vout": [ {
      "amount": 18941599636, 
      "target": {
        "key": "cbfdf920549b463ab4cf5b5d5874c90c99cf149c407a3019c44ad97573fee313"
      }
    }
  ], 
  "extra": [ 1, 170, 47, 122, 62, 8, 101, 190, 136, 15, 191, 148, 227, 76, 139, 46, 121, 211, 251, 66, 34, 195, 254, 102, 51, 95, 96, 200, 58, 240, 226, 169, 121, 3, 33, 0, 76, 29, 197, 26, 224, 58, 193, 74, 149, 178, 210, 246, 200, 191, 70, 218, 34, 45, 109, 95, 53, 37, 14, 190, 85, 208, 39, 211, 67, 41, 110, 20, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 10, 48, 230, 243, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}