Transaction Details
Tx hash
55911b14eccf891d10c27ddaf0fe0a7d407f09c891e721f8f62c9b72155f5354
Tx prefix hash
4df41af0396c31bd2da2cd2c3d932d7c157dfa8db1902818a54478d22834217b
Tx public key
e5beab69a2de115270cf406ee971d23bb27ed4531b31a659554b301360370188
Age [y:d:h:m:s]
05:302:17:29:25
Timestamp [UCT] (epoch)
2019-01-28 08:31:02 (1548664262)
Block
100463 (1497680 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
01e5beab69a2de115270cf406ee971d23bb27ed4531b31a659554b3013603701880321009df997396b97e9a1d15a20d885b45441d2cbf1025aa38e3357b14d2a87ab3ac7021b000000000000000000000000001e1d85af00000000000000000000
Outputs
1 output(s) for total of 19.318027539 ARQ
stealth address amount amount idx
00: 59c3d93472f6d8a236e0e451f6aa027c0d8f7668076b3c44435aff820e1515d8 19.318027539 496448 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": 100481, 
  "vin": [ {
      "gen": {
        "height": 100463
      }
    }
  ], 
  "vout": [ {
      "amount": 19318027539, 
      "target": {
        "key": "59c3d93472f6d8a236e0e451f6aa027c0d8f7668076b3c44435aff820e1515d8"
      }
    }
  ], 
  "extra": [ 1, 229, 190, 171, 105, 162, 222, 17, 82, 112, 207, 64, 110, 233, 113, 210, 59, 178, 126, 212, 83, 27, 49, 166, 89, 85, 75, 48, 19, 96, 55, 1, 136, 3, 33, 0, 157, 249, 151, 57, 107, 151, 233, 161, 209, 90, 32, 216, 133, 180, 84, 65, 210, 203, 241, 2, 90, 163, 142, 51, 87, 177, 77, 42, 135, 171, 58, 199, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 30, 29, 133, 175, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}