Transaction Details
Tx hash
4cb57ff8a1e787ef986cfd71eaae7457cefba9a765be2a54d8fded14edc911ce
Tx prefix hash
5c7efb4ebd6f9f886a69273777797f41fba1de5f9d767c5a68f59a574d897c7e
Tx public key
5b0e9b7e5f21cfda166a582267f036dfad9c0cd2d5399bbeedc9e1d503ea9483
Age [y:d:h:m:s]
05:298:12:41:15
Timestamp [UCT] (epoch)
2019-02-01 10:10:12 (1549015812)
Block
103422 (1494623 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
015b0e9b7e5f21cfda166a582267f036dfad9c0cd2d5399bbeedc9e1d503ea948303210096faf04293d33f560a2687e830ac682b6383ec8bf4a9108faf7e99225085709b021b000000000000000000000000000b3b514600000000000000000000
Outputs
1 output(s) for total of 19.290465564 ARQ
stealth address amount amount idx
00: f99ae756a85c1f68c26276dc357ec8d97982c796bf7f8ecdf0f286c040b6bb3e 19.290465564 511037 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": 103440, 
  "vin": [ {
      "gen": {
        "height": 103422
      }
    }
  ], 
  "vout": [ {
      "amount": 19290465564, 
      "target": {
        "key": "f99ae756a85c1f68c26276dc357ec8d97982c796bf7f8ecdf0f286c040b6bb3e"
      }
    }
  ], 
  "extra": [ 1, 91, 14, 155, 126, 95, 33, 207, 218, 22, 106, 88, 34, 103, 240, 54, 223, 173, 156, 12, 210, 213, 57, 155, 190, 237, 201, 225, 213, 3, 234, 148, 131, 3, 33, 0, 150, 250, 240, 66, 147, 211, 63, 86, 10, 38, 135, 232, 48, 172, 104, 43, 99, 131, 236, 139, 244, 169, 16, 143, 175, 126, 153, 34, 80, 133, 112, 155, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 59, 81, 70, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}