Transaction Details
Tx hash
e22035b4dac3a32575eb393009fcbf38de529321d645fa5b245396e297ed983e
Tx prefix hash
55e01964553f9f12d7cf49899877b44466b0a63baa1f838c18ac35e3565365dd
Tx public key
6de836b3c47f1dbf65b897ba32f960cb00a89196a7a5613b50fd1e9ce5f7bda0
Age [y:d:h:m:s]
05:273:12:59:03
Timestamp [UCT] (epoch)
2019-01-07 23:26:00 (1546903560)
Block
85968 (1477197 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
016de836b3c47f1dbf65b897ba32f960cb00a89196a7a5613b50fd1e9ce5f7bda0032100ebc90bcbd816c7428d54084508c047178e3f9677ffeb25bc5417c3b750d578f3021b0000000000000000000000000013f30e0c00000000000000000000
Outputs
1 output(s) for total of 19.451684624 ARQ
stealth address amount amount idx
00: 1691ce4d2e3b7cc094475428345d765e5d2eb36bddf168a4203c21ceac85829f 19.451684624 425090 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": 85986, 
  "vin": [ {
      "gen": {
        "height": 85968
      }
    }
  ], 
  "vout": [ {
      "amount": 19451684624, 
      "target": {
        "key": "1691ce4d2e3b7cc094475428345d765e5d2eb36bddf168a4203c21ceac85829f"
      }
    }
  ], 
  "extra": [ 1, 109, 232, 54, 179, 196, 127, 29, 191, 101, 184, 151, 186, 50, 249, 96, 203, 0, 168, 145, 150, 167, 165, 97, 59, 80, 253, 30, 156, 229, 247, 189, 160, 3, 33, 0, 235, 201, 11, 203, 216, 22, 199, 66, 141, 84, 8, 69, 8, 192, 71, 23, 142, 63, 150, 119, 255, 235, 37, 188, 84, 23, 195, 183, 80, 213, 120, 243, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 19, 243, 14, 12, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}