Transaction Details
Tx hash
6e6601d9d4acfc406541974b23679f265fdd26fd6682114fb7eb98eda94c416b
Tx prefix hash
c7e95c4396e908915005d0787605e555309e19a247bf0824be8aab94eea9765a
Tx public key
0b32f6a056a6a3f8d17b6fe3b73532118248f2deff391d347e8893fd7df9dbce
Age [y:d:h:m:s]
05:324:03:26:34
Timestamp [UCT] (epoch)
2019-01-10 14:09:54 (1547129394)
Block
87818 (1512903 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
010b32f6a056a6a3f8d17b6fe3b73532118248f2deff391d347e8893fd7df9dbce032100866706e5046aa00de6079bf4a45284eb265a40443d19b3e1aaee68c9410c2769021b0000000000000000000000000021c9579800000000000000000000
Outputs
1 output(s) for total of 19.434696287 ARQ
stealth address amount amount idx
00: b579524d661928c350ab9b6cd2b5dca5171af9f18892038bdc526482f4b506de 19.434696287 433738 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": 87836, 
  "vin": [ {
      "gen": {
        "height": 87818
      }
    }
  ], 
  "vout": [ {
      "amount": 19434696287, 
      "target": {
        "key": "b579524d661928c350ab9b6cd2b5dca5171af9f18892038bdc526482f4b506de"
      }
    }
  ], 
  "extra": [ 1, 11, 50, 246, 160, 86, 166, 163, 248, 209, 123, 111, 227, 183, 53, 50, 17, 130, 72, 242, 222, 255, 57, 29, 52, 126, 136, 147, 253, 125, 249, 219, 206, 3, 33, 0, 134, 103, 6, 229, 4, 106, 160, 13, 230, 7, 155, 244, 164, 82, 132, 235, 38, 90, 64, 68, 61, 25, 179, 225, 170, 238, 104, 201, 65, 12, 39, 105, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 33, 201, 87, 152, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}