Transaction Details
Tx hash
573ce79ee386fef952a7feb1f583a96fea3384751bf8293eb018041649f58cd4
Tx prefix hash
3afcb4b1c1c9e62a32ebee738e112c5d70680daec7a0883016b55a58a058acda
Tx public key
84ea55c5992130d04ef568eadc5bbb64c504bddbd9dc65f8f6914b0315b91402
Age [y:d:h:m:s]
05:290:04:11:10
Timestamp [UCT] (epoch)
2019-02-10 14:31:18 (1549809078)
Block
109950 (1488684 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
0184ea55c5992130d04ef568eadc5bbb64c504bddbd9dc65f8f6914b0315b9140203210008caeccab30bb7010f4ec57a2e07035e19609c49b117e9c54ddbdc83ebbfb1b4021b00000000000000000000000000176adb0b00000000000000000000
Outputs
1 output(s) for total of 19.230889132 ARQ
stealth address amount amount idx
00: 88ca531e716d96a7d34c8cf19cf48e903b4ad6f435d930b0f2db41d0a755c966 19.230889132 537707 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": 109968, 
  "vin": [ {
      "gen": {
        "height": 109950
      }
    }
  ], 
  "vout": [ {
      "amount": 19230889132, 
      "target": {
        "key": "88ca531e716d96a7d34c8cf19cf48e903b4ad6f435d930b0f2db41d0a755c966"
      }
    }
  ], 
  "extra": [ 1, 132, 234, 85, 197, 153, 33, 48, 208, 78, 245, 104, 234, 220, 91, 187, 100, 197, 4, 189, 219, 217, 220, 101, 248, 246, 145, 75, 3, 21, 185, 20, 2, 3, 33, 0, 8, 202, 236, 202, 179, 11, 183, 1, 15, 78, 197, 122, 46, 7, 3, 94, 25, 96, 156, 73, 177, 23, 233, 197, 77, 219, 220, 131, 235, 191, 177, 180, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 23, 106, 219, 11, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}