Transaction Details
Tx hash
8c67e18fa2195ec414aa20eb79a59f0ab40b55f8ff6999b1778ee54b85a71f5c
Tx prefix hash
ab8b54dd2a2667ab912b41dfb9d34d4250911366fcf3e2fcf6aa2529dee6a8d2
Tx public key
bb5c7f7ad4630fd026f5f8eee0f949a26110c017b4085402f1b3e350d1c9e64e
Age [y:d:h:m:s]
05:316:03:44:16
Timestamp [UCT] (epoch)
2019-01-18 19:57:56 (1547841476)
Block
93691 (1507200 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01bb5c7f7ad4630fd026f5f8eee0f949a26110c017b4085402f1b3e350d1c9e64e032100eacf27d4f6dd2328b30257d9721b70a312b538a6abb408a6369ae95d6ef51b32021b000000000000000000000000001e51cc6700000000000000000000
Outputs
1 output(s) for total of 19.380183310 ARQ
stealth address amount amount idx
00: c2c364f724074bb105907d96102eef26bab09d6f445a1f444e3bd5c250febc9e 19.380183310 462138 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": 93709, 
  "vin": [ {
      "gen": {
        "height": 93691
      }
    }
  ], 
  "vout": [ {
      "amount": 19380183310, 
      "target": {
        "key": "c2c364f724074bb105907d96102eef26bab09d6f445a1f444e3bd5c250febc9e"
      }
    }
  ], 
  "extra": [ 1, 187, 92, 127, 122, 212, 99, 15, 208, 38, 245, 248, 238, 224, 249, 73, 162, 97, 16, 192, 23, 180, 8, 84, 2, 241, 179, 227, 80, 209, 201, 230, 78, 3, 33, 0, 234, 207, 39, 212, 246, 221, 35, 40, 179, 2, 87, 217, 114, 27, 112, 163, 18, 181, 56, 166, 171, 180, 8, 166, 54, 154, 233, 93, 110, 245, 27, 50, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 30, 81, 204, 103, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}