Transaction Details
Tx hash
1bbbb9b5b5b5895491b5e4cb1976113baa1860b4a191b41cf31abb6a6af90dcd
Tx prefix hash
e9c5a1fcc4620ebfdcdf48125c1fe002cac6744ecf6b3c2bf7aeb8b3dfcc6930
Tx public key
e9fcb1a4a28c14d5b56405e95a6f66b0a1c6eaad41a2f4fad436f6213a3b9c5a
Age [y:d:h:m:s]
05:060:21:11:17
Timestamp [UCT] (epoch)
2019-08-04 02:19:12 (1564885152)
Block
234691 (1325306 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
01e9fcb1a4a28c14d5b56405e95a6f66b0a1c6eaad41a2f4fad436f6213a3b9c5a021100000009244b886e00000000000000000003210074fd0c04324a85c4c6d1a04ceb1f5f659e6388145ac99a3d1d07fc43c377ec46
Outputs
1 output(s) for total of 18.120013763 ARQ
stealth address amount amount idx
00: e1fd4c0e0b594390c6d323ac82e1532a4ef1d4742b52436cdefca0162ed15803 18.120013763 1084956 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": 234709, 
  "vin": [ {
      "gen": {
        "height": 234691
      }
    }
  ], 
  "vout": [ {
      "amount": 18120013763, 
      "target": {
        "key": "e1fd4c0e0b594390c6d323ac82e1532a4ef1d4742b52436cdefca0162ed15803"
      }
    }
  ], 
  "extra": [ 1, 233, 252, 177, 164, 162, 140, 20, 213, 181, 100, 5, 233, 90, 111, 102, 176, 161, 198, 234, 173, 65, 162, 244, 250, 212, 54, 246, 33, 58, 59, 156, 90, 2, 17, 0, 0, 0, 9, 36, 75, 136, 110, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 116, 253, 12, 4, 50, 74, 133, 196, 198, 209, 160, 76, 235, 31, 95, 101, 158, 99, 136, 20, 90, 201, 154, 61, 29, 7, 252, 67, 195, 119, 236, 70
  ], 
  "rct_signatures": {
    "type": 0
  }
}