Transaction Details
Tx hash
afabb7a60ca3d46b9904eb46016144042ca06ab7b670dcb183975849318e8922
Tx prefix hash
fb856c4efc30b916471a83b2d6a570bbdd390c760bfee7ea499759769370de22
Tx public key
8198454b48e065f8e9e65f0c58ba571807ca4bf4d402e341e2894ccf70b194ed
Age [y:d:h:m:s]
05:337:16:58:57
Timestamp [UCT] (epoch)
2018-12-24 22:16:31 (1545689791)
Block
76022 (1522508 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1436 kB
Tx version
2
RingCT type
0
Extra
018198454b48e065f8e9e65f0c58ba571807ca4bf4d402e341e2894ccf70b194ed032100bfcd5e2eb2fcb9af7c2dccd8476adef5730de7e1e054087949a8d2467ca22230021b0000000000000000000000000002e71ede00000000000000000000
Outputs
1 output(s) for total of 19.544155745 ARQ
stealth address amount amount idx
00: eef384c3651d6c81cd35e469f10a4cfefe7372d9efde3b4f625fca0baebb3bed 19.544155745 383853 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": 76040, 
  "vin": [ {
      "gen": {
        "height": 76022
      }
    }
  ], 
  "vout": [ {
      "amount": 19544155745, 
      "target": {
        "key": "eef384c3651d6c81cd35e469f10a4cfefe7372d9efde3b4f625fca0baebb3bed"
      }
    }
  ], 
  "extra": [ 1, 129, 152, 69, 75, 72, 224, 101, 248, 233, 230, 95, 12, 88, 186, 87, 24, 7, 202, 75, 244, 212, 2, 227, 65, 226, 137, 76, 207, 112, 177, 148, 237, 3, 33, 0, 191, 205, 94, 46, 178, 252, 185, 175, 124, 45, 204, 216, 71, 106, 222, 245, 115, 13, 231, 225, 224, 84, 8, 121, 73, 168, 210, 70, 124, 162, 34, 48, 2, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2, 231, 30, 222, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}