Transaction Details
Tx hash
e58e9b66ce7ef6cfbf298f54cd9cf808f04b5fc8cd6cc53f3bd6453372c3fde2
Tx prefix hash
cc099af19decb4127bdd577ae2a0da3e1853bcfbca96613647567d25ba8bf5fc
Tx public key
b13cf13edfe7f86992b6560e8cabcd38bd7e83144c8597114da11b1fd50bd8a3
Age [y:d:h:m:s]
05:333:13:05:56
Timestamp [UCT] (epoch)
2018-12-29 04:53:00 (1546059180)
Block
79017 (1519601 confirmations)
Fee (per_kB)
0.000000000 (0.000000000)
Tx size
0.1328 kB
Tx version
2
RingCT type
0
Extra
01b13cf13edfe7f86992b6560e8cabcd38bd7e83144c8597114da11b1fd50bd8a3032100390c5e21f44d9c5575a51663f76236d9167dc1120fcc9870c9b12a42cce55f1b021000000005933f0e000000000000000000
Outputs
1 output(s) for total of 19.516264117 ARQ
stealth address amount amount idx
00: 9285ddb7bde09d24bfc9107b57039b76874bb48e57fd57791b915d8c27bcf4fa 19.516264117 391853 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": 79035, 
  "vin": [ {
      "gen": {
        "height": 79017
      }
    }
  ], 
  "vout": [ {
      "amount": 19516264117, 
      "target": {
        "key": "9285ddb7bde09d24bfc9107b57039b76874bb48e57fd57791b915d8c27bcf4fa"
      }
    }
  ], 
  "extra": [ 1, 177, 60, 241, 62, 223, 231, 248, 105, 146, 182, 86, 14, 140, 171, 205, 56, 189, 126, 131, 20, 76, 133, 151, 17, 77, 161, 27, 31, 213, 11, 216, 163, 3, 33, 0, 57, 12, 94, 33, 244, 77, 156, 85, 117, 165, 22, 99, 247, 98, 54, 217, 22, 125, 193, 18, 15, 204, 152, 112, 201, 177, 42, 66, 204, 229, 95, 27, 2, 16, 0, 0, 0, 5, 147, 63, 14, 0, 0, 0, 0, 0, 0, 0, 0, 0
  ], 
  "rct_signatures": {
    "type": 0
  }
}