Transaction Details
Tx hash
41fa5ff843f333cce9214d3d8c2a2b877172618dae2fc5d9930a5079bc318d6c
Tx prefix hash
c55a635bf90e92773acd4497f76c30f5781552ecbd297737445039c19730b525
Tx public key
0c7b282f060493d58a4997125a1d8598750f283f67483b9569ae278adb4f08c0
Age [y:d:h:m:s]
05:350:16:59:02
Timestamp [UCT] (epoch)
2018-12-10 19:01:26 (1544468486)
Block
65956 (1531760 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
010c7b282f060493d58a4997125a1d8598750f283f67483b9569ae278adb4f08c0032100fe96f29ab9a54238fd9c99e9112ac54ac6519e8a038824aa5a277b67127dc980021000000009f61c01000000000000000000
Outputs
1 output(s) for total of 19.638190138 ARQ
stealth address amount amount idx
00: 3e53d8680f3c124da342d1aa7d920d0a61480e7272343aa5e8306549183f35b0 19.638190138 348468 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": 65974, 
  "vin": [ {
      "gen": {
        "height": 65956
      }
    }
  ], 
  "vout": [ {
      "amount": 19638190138, 
      "target": {
        "key": "3e53d8680f3c124da342d1aa7d920d0a61480e7272343aa5e8306549183f35b0"
      }
    }
  ], 
  "extra": [ 1, 12, 123, 40, 47, 6, 4, 147, 213, 138, 73, 151, 18, 90, 29, 133, 152, 117, 15, 40, 63, 103, 72, 59, 149, 105, 174, 39, 138, 219, 79, 8, 192, 3, 33, 0, 254, 150, 242, 154, 185, 165, 66, 56, 253, 156, 153, 233, 17, 42, 197, 74, 198, 81, 158, 138, 3, 136, 36, 170, 90, 39, 123, 103, 18, 125, 201, 128, 2, 16, 0, 0, 0, 9, 246, 28, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}