Transaction Details
Tx hash
b9e49d998efa55cc4439fefff5aa37ab809349aab7d81e2fb7b5397976403a95
Tx prefix hash
9834d1d0bd928c789d66b39418adefdd8d667a55e4e9e1465d294a78136012c5
Tx public key
4a29ad83f8116fa769e0423ff884e5af73164f5100ed9143eb1e3a703639493c
Age [y:d:h:m:s]
05:311:14:40:37
Timestamp [UCT] (epoch)
2019-01-23 07:31:50 (1548228710)
Block
96888 (1503963 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
014a29ad83f8116fa769e0423ff884e5af73164f5100ed9143eb1e3a703639493c032100cea3e7519ef8898f0fdf40f4b19e189ee7237c3ec40c1d6be3b868a830fdeee6021b000000000000000000000000001c8f4a7300000000000000000000
Outputs
1 output(s) for total of 19.350661721 ARQ
stealth address amount amount idx
00: cf5fba212df659e192219c552872f5809dd8a77a118b923585e68cf69b2e2d98 19.350661721 478093 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": 96906, 
  "vin": [ {
      "gen": {
        "height": 96888
      }
    }
  ], 
  "vout": [ {
      "amount": 19350661721, 
      "target": {
        "key": "cf5fba212df659e192219c552872f5809dd8a77a118b923585e68cf69b2e2d98"
      }
    }
  ], 
  "extra": [ 1, 74, 41, 173, 131, 248, 17, 111, 167, 105, 224, 66, 63, 248, 132, 229, 175, 115, 22, 79, 81, 0, 237, 145, 67, 235, 30, 58, 112, 54, 57, 73, 60, 3, 33, 0, 206, 163, 231, 81, 158, 248, 137, 143, 15, 223, 64, 244, 177, 158, 24, 158, 231, 35, 124, 62, 196, 12, 29, 107, 227, 184, 104, 168, 48, 253, 238, 230, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 28, 143, 74, 115, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}