Transaction Details
Tx hash
d013538bb38740df6d85ba03bd234d2552c9a7dc354907e86fc5fea97599a898
Tx prefix hash
28b763f3119ec1c112d5e4a9206fc1bbc38f75cefd0d8e772db130398f625c0b
Tx public key
492e73d358c8c31da0cfa831a2f2dec1acdc1272c1e1554f0d6c8f5e3c92d703
Age [y:d:h:m:s]
05:177:18:02:02
Timestamp [UCT] (epoch)
2019-04-13 10:16:47 (1555150607)
Block
153963 (1408962 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01492e73d358c8c31da0cfa831a2f2dec1acdc1272c1e1554f0d6c8f5e3c92d70303210004bb6e688e2677e73ecf47c39e53514a88684330a6d09ec40c3dd25a0d6cdd5f021b00000000000000000000000000f9dc2ff600000000000000000000
Outputs
1 output(s) for total of 18.831126760 ARQ
stealth address amount amount idx
00: ed26303f8c002e534ed6ad8faf4c6d474b217ab613e388f7f53f6c2183bc3870 18.831126760 704656 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": 153981, 
  "vin": [ {
      "gen": {
        "height": 153963
      }
    }
  ], 
  "vout": [ {
      "amount": 18831126760, 
      "target": {
        "key": "ed26303f8c002e534ed6ad8faf4c6d474b217ab613e388f7f53f6c2183bc3870"
      }
    }
  ], 
  "extra": [ 1, 73, 46, 115, 211, 88, 200, 195, 29, 160, 207, 168, 49, 162, 242, 222, 193, 172, 220, 18, 114, 193, 225, 85, 79, 13, 108, 143, 94, 60, 146, 215, 3, 3, 33, 0, 4, 187, 110, 104, 142, 38, 119, 231, 62, 207, 71, 195, 158, 83, 81, 74, 136, 104, 67, 48, 166, 208, 158, 196, 12, 61, 210, 90, 13, 108, 221, 95, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 249, 220, 47, 246, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}