Transaction Details
Tx hash
dd6488481f843f81260beb05eb489435f221d418f9d993791cc46dc27cb67779
Tx prefix hash
a5a4067ff5460809e65042a3ab6de03471ac812f1ca8437834bdcf350e486b36
Tx public key
f46d5374b9f2f6189f2d5f7d8408b610fa3533b6037176475e17eb4b5b1bb820
Age [y:d:h:m:s]
05:120:02:16:41
Timestamp [UCT] (epoch)
2019-08-02 05:52:46 (1564725166)
Block
233349 (1367103 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01f46d5374b9f2f6189f2d5f7d8408b610fa3533b6037176475e17eb4b5b1bb82003210063e8342a4765a654c9af2aced4d177357a31decd8a730c766623ae5b3a6391d1021b00000000000000000000000026fe3771c800000000000000000000
Outputs
1 output(s) for total of 18.131612754 ARQ
stealth address amount amount idx
00: 3a690976f42750e42f7549a1df5567bcbfb7d6096d9ea9535e438df2397fbe51 18.131612754 1082091 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": 233367, 
  "vin": [ {
      "gen": {
        "height": 233349
      }
    }
  ], 
  "vout": [ {
      "amount": 18131612754, 
      "target": {
        "key": "3a690976f42750e42f7549a1df5567bcbfb7d6096d9ea9535e438df2397fbe51"
      }
    }
  ], 
  "extra": [ 1, 244, 109, 83, 116, 185, 242, 246, 24, 159, 45, 95, 125, 132, 8, 182, 16, 250, 53, 51, 182, 3, 113, 118, 71, 94, 23, 235, 75, 91, 27, 184, 32, 3, 33, 0, 99, 232, 52, 42, 71, 101, 166, 84, 201, 175, 42, 206, 212, 209, 119, 53, 122, 49, 222, 205, 138, 115, 12, 118, 102, 35, 174, 91, 58, 99, 145, 209, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 38, 254, 55, 113, 200, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}