Transaction Details
Tx hash
00c0c2ff6866c8bf14806e52bd2f40fe747f044d1995a321d39f7b21d8c9a57c
Tx prefix hash
e1e0ad18f76035a089e2f598d215d9f6c413546c09ced8741dbc1c5122fea08a
Tx public key
89e9a6c0d6effd7665e413cf1dfc1a5fa925768df7fb0a806aa373258c8d5951
Age [y:d:h:m:s]
05:086:08:30:10
Timestamp [UCT] (epoch)
2019-08-26 20:30:17 (1566851417)
Block
251022 (1342936 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0189e9a6c0d6effd7665e413cf1dfc1a5fa925768df7fb0a806aa373258c8d595103210080b02f34fea5790fcbd0cc9c1198c9a31e31e072dd4bbf56f41465392597b64d021b00000000000000000000000005b47e520e00000000000000000000
Outputs
1 output(s) for total of 20.408074941 ARQ
stealth address amount amount idx
00: ddab9adf15fd44fa7089d5c8ea94179e0b306a9d09d7116ffcf3c1a258c57add 20.408074941 1116441 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": 251040, 
  "vin": [ {
      "gen": {
        "height": 251022
      }
    }
  ], 
  "vout": [ {
      "amount": 20408074941, 
      "target": {
        "key": "ddab9adf15fd44fa7089d5c8ea94179e0b306a9d09d7116ffcf3c1a258c57add"
      }
    }
  ], 
  "extra": [ 1, 137, 233, 166, 192, 214, 239, 253, 118, 101, 228, 19, 207, 29, 252, 26, 95, 169, 37, 118, 141, 247, 251, 10, 128, 106, 163, 115, 37, 140, 141, 89, 81, 3, 33, 0, 128, 176, 47, 52, 254, 165, 121, 15, 203, 208, 204, 156, 17, 152, 201, 163, 30, 49, 224, 114, 221, 75, 191, 86, 244, 20, 101, 57, 37, 151, 182, 77, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 180, 126, 82, 14, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}