Transaction Details
Tx hash
cbbc2ca585ad0ddd47f9959d572e117c7935e6d699d99868a3eb5e5a8f8c3ff4
Tx prefix hash
4ecd82da848fda074e5f79ae53b7dd7fc6caa2515981a91b629322cd8cdbaf84
Tx public key
a4411b0789c0d401842e0f54a5dcd7cdca11c4e4a49b10df504a2a68c33e38f6
Age [y:d:h:m:s]
05:095:03:23:28
Timestamp [UCT] (epoch)
2019-08-26 23:40:16 (1566862816)
Block
251122 (1349172 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01a4411b0789c0d401842e0f54a5dcd7cdca11c4e4a49b10df504a2a68c33e38f6032100d0a3e9f5c4b3c0bfb4c7c9852881ea95c6bda5cb505ab56babe74854ecbf6127021b0000000000000000000000000bae78276400000000000000000000
Outputs
1 output(s) for total of 20.407083232 ARQ
stealth address amount amount idx
00: b4331004a20428493c47e57a2aa532bb103c07fba70fe02b72f58dcc75c6091d 20.407083232 1116592 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": 251140, 
  "vin": [ {
      "gen": {
        "height": 251122
      }
    }
  ], 
  "vout": [ {
      "amount": 20407083232, 
      "target": {
        "key": "b4331004a20428493c47e57a2aa532bb103c07fba70fe02b72f58dcc75c6091d"
      }
    }
  ], 
  "extra": [ 1, 164, 65, 27, 7, 137, 192, 212, 1, 132, 46, 15, 84, 165, 220, 215, 205, 202, 17, 196, 228, 164, 155, 16, 223, 80, 74, 42, 104, 195, 62, 56, 246, 3, 33, 0, 208, 163, 233, 245, 196, 179, 192, 191, 180, 199, 201, 133, 40, 129, 234, 149, 198, 189, 165, 203, 80, 90, 181, 107, 171, 231, 72, 84, 236, 191, 97, 39, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 174, 120, 39, 100, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}