Transaction Details
Tx hash
587ae5fa8e7a8f7a91673e5e8671abdb09f050462cd0667a1be05452530fabf8
Tx prefix hash
dd4b64e01b071cb0a061dc9a2d735a62342dfbf6285b63e37f74bf4b056906ca
Tx public key
ce4a3ea9d5f4a37090de68b051db5418a63d48d2a2f1d6ceba55b0af7bfb4026
Age [y:d:h:m:s]
05:294:12:57:40
Timestamp [UCT] (epoch)
2019-02-06 08:44:47 (1549442687)
Block
106915 (1491806 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01ce4a3ea9d5f4a37090de68b051db5418a63d48d2a2f1d6ceba55b0af7bfb40260321000934dbbe0c10010707b1d53b77c7d5f64a20e6f04b91f2504bdf4b8d043f9841021b0000000000000000000000000005ebd99800000000000000000000
Outputs
1 output(s) for total of 19.258454878 ARQ
stealth address amount amount idx
00: fcacd64e26e1a5df16dfc137aa25211bded412a4a8a22683ce428027f9a90467 19.258454878 525840 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": 106933, 
  "vin": [ {
      "gen": {
        "height": 106915
      }
    }
  ], 
  "vout": [ {
      "amount": 19258454878, 
      "target": {
        "key": "fcacd64e26e1a5df16dfc137aa25211bded412a4a8a22683ce428027f9a90467"
      }
    }
  ], 
  "extra": [ 1, 206, 74, 62, 169, 213, 244, 163, 112, 144, 222, 104, 176, 81, 219, 84, 24, 166, 61, 72, 210, 162, 241, 214, 206, 186, 85, 176, 175, 123, 251, 64, 38, 3, 33, 0, 9, 52, 219, 190, 12, 16, 1, 7, 7, 177, 213, 59, 119, 199, 213, 246, 74, 32, 230, 240, 75, 145, 242, 80, 75, 223, 75, 141, 4, 63, 152, 65, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 5, 235, 217, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}