Transaction Details
Tx hash
095e07f360c3150fb08f883c4579f28ddacd575702608fce066c48500264fd2f
Tx prefix hash
4766813e06849d222cfae75955e2f20ad7981666f163fc67f5ab7d9189e11eb2
Tx public key
1d712fd31adf6df5d12d9194bba3817c810a78360a3385df1d98e9e8b228ebe7
Age [y:d:h:m:s]
05:160:07:24:51
Timestamp [UCT] (epoch)
2019-06-20 07:11:36 (1561014696)
Block
202509 (1396006 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1338 kB
Tx version
2
RingCT type
0
Extra
011d712fd31adf6df5d12d9194bba3817c810a78360a3385df1d98e9e8b228ebe702110000000bd4c33ed7000000000000000000032100edd15c9461dde9a1d326e3d1f23a89ee3b342abc0770f828ea0c72b033cb1445
Outputs
1 output(s) for total of 18.400220298 ARQ
stealth address amount amount idx
00: 3471b0b52dfb187e9245757594eecca2dc879c8fcd5e084f5e198cca84d085fb 18.400220298 921886 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": 202527, 
  "vin": [ {
      "gen": {
        "height": 202509
      }
    }
  ], 
  "vout": [ {
      "amount": 18400220298, 
      "target": {
        "key": "3471b0b52dfb187e9245757594eecca2dc879c8fcd5e084f5e198cca84d085fb"
      }
    }
  ], 
  "extra": [ 1, 29, 113, 47, 211, 26, 223, 109, 245, 209, 45, 145, 148, 187, 163, 129, 124, 129, 10, 120, 54, 10, 51, 133, 223, 29, 152, 233, 232, 178, 40, 235, 231, 2, 17, 0, 0, 0, 11, 212, 195, 62, 215, 0, 0, 0, 0, 0, 0, 0, 0, 0, 3, 33, 0, 237, 209, 92, 148, 97, 221, 233, 161, 211, 38, 227, 209, 242, 58, 137, 238, 59, 52, 42, 188, 7, 112, 248, 40, 234, 12, 114, 176, 51, 203, 20, 69
  ], 
  "rct_signatures": {
    "type": 0
  }
}