Transaction Details
Tx hash
7923ba9662e4cd06ede0b448e7861076612394aa4064e91cd86f72f091037fdb
Tx prefix hash
13ba171d871e421db82f923df3f01aba81129fbbd37676a9f2df5239dd86a329
Tx public key
8b2f2b4928206cd3d267f5b77051fbf577e80331ac7f4d108523de9b56fc04f8
Age [y:d:h:m:s]
05:267:16:58:13
Timestamp [UCT] (epoch)
2019-01-13 06:17:16 (1547360236)
Block
89703 (1473073 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
018b2f2b4928206cd3d267f5b77051fbf577e80331ac7f4d108523de9b56fc04f803210022f92a47842ac158e42e5a8dec66dad452f36904ea49a98e25a1b4a363ab3472021b000000000000000000000000000111dca400000000000000000000
Outputs
1 output(s) for total of 19.417072254 ARQ
stealth address amount amount idx
00: dd8cd0a65e63e3e9f915776e0750a9e2b2e87e685e8011212982efba8f83a118 19.417072254 443542 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": 89721, 
  "vin": [ {
      "gen": {
        "height": 89703
      }
    }
  ], 
  "vout": [ {
      "amount": 19417072254, 
      "target": {
        "key": "dd8cd0a65e63e3e9f915776e0750a9e2b2e87e685e8011212982efba8f83a118"
      }
    }
  ], 
  "extra": [ 1, 139, 47, 43, 73, 40, 32, 108, 211, 210, 103, 245, 183, 112, 81, 251, 245, 119, 232, 3, 49, 172, 127, 77, 16, 133, 35, 222, 155, 86, 252, 4, 248, 3, 33, 0, 34, 249, 42, 71, 132, 42, 193, 88, 228, 46, 90, 141, 236, 102, 218, 212, 82, 243, 105, 4, 234, 73, 169, 142, 37, 161, 180, 163, 99, 171, 52, 114, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 17, 220, 164, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}