Transaction Details
Tx hash
af4e31000d4e1952cf8e47b06b60404d8e455d439001028904288ad9173b351b
Tx prefix hash
aa1b1c74e2f07186b4d5661e9edbacdc5d02de9a15de78052c146f4b84eb45b6
Tx public key
0d960346d3dbaa29adf88682d176741503c323e888850af77113129ca954c824
Age [y:d:h:m:s]
05:105:21:00:29
Timestamp [UCT] (epoch)
2019-03-24 06:47:55 (1553410075)
Block
139705 (1358101 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010d960346d3dbaa29adf88682d176741503c323e888850af77113129ca954c824032100466d075d37bb1df29d39fd9be671d4c63ce803df93e67e5bc4a9a94e4f3c2212021b0000000000000000000000000006f9e17300000000000000000000
Outputs
1 output(s) for total of 18.959591008 ARQ
stealth address amount amount idx
00: bca914314b595ea5b95c0ade2ed47b24128a91e65e8f0ba604d11f34813093a1 18.959591008 646668 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": 139723, 
  "vin": [ {
      "gen": {
        "height": 139705
      }
    }
  ], 
  "vout": [ {
      "amount": 18959591008, 
      "target": {
        "key": "bca914314b595ea5b95c0ade2ed47b24128a91e65e8f0ba604d11f34813093a1"
      }
    }
  ], 
  "extra": [ 1, 13, 150, 3, 70, 211, 219, 170, 41, 173, 248, 134, 130, 209, 118, 116, 21, 3, 195, 35, 232, 136, 133, 10, 247, 113, 19, 18, 156, 169, 84, 200, 36, 3, 33, 0, 70, 109, 7, 93, 55, 187, 29, 242, 157, 57, 253, 155, 230, 113, 212, 198, 60, 232, 3, 223, 147, 230, 126, 91, 196, 169, 169, 78, 79, 60, 34, 18, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 6, 249, 225, 115, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}