Transaction Details
Tx hash
4b9f61111e5f036a6aad917b16a3a66d0bd009017a2d58bcf0c6474a69dfce47
Tx prefix hash
e05e372a6b11bdbe1ebf46c7ebe23dc472d9b8818c49363191b7466aaddfc1eb
Tx public key
c0a2b4dce96d1a6e1df4e091a7dfbc8debffb6ce0cce9308d64deddf7601b4d4
Age [y:d:h:m:s]
05:070:06:51:11
Timestamp [UCT] (epoch)
2019-09-20 20:57:01 (1569013021)
Block
268448 (1331875 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01c0a2b4dce96d1a6e1df4e091a7dfbc8debffb6ce0cce9308d64deddf7601b4d40211000003c7aa9cfb43000000000000000000032100d70dc0f375b9d6399a6d2275883de047b7c3fd92924709d0ed8d28d9958704df
Outputs
1 output(s) for total of 20.239180921 ARQ
stealth address amount amount idx
00: 067b7e3846c3457b93838e7acb542ae991e3143065a8f4c029ed8ba2012de111 20.239180921 1202553 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": 268466, 
  "vin": [ {
      "gen": {
        "height": 268448
      }
    }
  ], 
  "vout": [ {
      "amount": 20239180921, 
      "target": {
        "key": "067b7e3846c3457b93838e7acb542ae991e3143065a8f4c029ed8ba2012de111"
      }
    }
  ], 
  "extra": [ 1, 192, 162, 180, 220, 233, 109, 26, 110, 29, 244, 224, 145, 167, 223, 188, 141, 235, 255, 182, 206, 12, 206, 147, 8, 214, 77, 237, 223, 118, 1, 180, 212, 2, 17, 0, 0, 3, 199, 170, 156, 251, 67, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 215, 13, 192, 243, 117, 185, 214, 57, 154, 109, 34, 117, 136, 61, 224, 71, 183, 195, 253, 146, 146, 71, 9, 208, 237, 141, 40, 217, 149, 135, 4, 223
  ], 
  "rct_signatures": {
    "type": 0
  }
}