Transaction Details
Tx hash
b72c0b0be4ab3ac260a464055c97104442d09d05cc8a40d1f5b51b77565b85c2
Tx prefix hash
d14971d1e903620f9069ec338964be17e6024842fe7130e34015f46deb934b87
Tx public key
90b409636cb51227eb2ce9f89d33008f6d1d3c57aa3276b0002eef66adc50be5
Age [y:d:h:m:s]
05:059:09:54:00
Timestamp [UCT] (epoch)
2019-10-04 10:06:28 (1570183588)
Block
278142 (1324035 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
0190b409636cb51227eb2ce9f89d33008f6d1d3c57aa3276b0002eef66adc50be50211000010ffaa9cfb43000000000000000000032100ef68f7521f3ae381bb51ddb0502874b0279e7aec723ef5b5bcfa3f7dfdb8d822
Outputs
1 output(s) for total of 20.145847380 ARQ
stealth address amount amount idx
00: e053036d73ad0adb7c3be6666022b910279b17d9b267af53f6d1298fd5a959bc 20.145847380 1251340 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": 278160, 
  "vin": [ {
      "gen": {
        "height": 278142
      }
    }
  ], 
  "vout": [ {
      "amount": 20145847380, 
      "target": {
        "key": "e053036d73ad0adb7c3be6666022b910279b17d9b267af53f6d1298fd5a959bc"
      }
    }
  ], 
  "extra": [ 1, 144, 180, 9, 99, 108, 181, 18, 39, 235, 44, 233, 248, 157, 51, 0, 143, 109, 29, 60, 87, 170, 50, 118, 176, 0, 46, 239, 102, 173, 197, 11, 229, 2, 17, 0, 0, 16, 255, 170, 156, 251, 67, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 239, 104, 247, 82, 31, 58, 227, 129, 187, 81, 221, 176, 80, 40, 116, 176, 39, 158, 122, 236, 114, 62, 245, 181, 188, 250, 63, 125, 253, 184, 216, 34
  ], 
  "rct_signatures": {
    "type": 0
  }
}