Tx hash: 508f9044dd5340ffb9506e14adb4922c85b6043d54b98b620fd399d7c2001e24

Tx prefix hash: 508f9044dd5340ffb9506e14adb4922c85b6043d54b98b620fd399d7c2001e24
Tx public key: a5c2d8205a98f3866e4eb8d4dc66ba069a8b1285b3139ef7ac12ca006c968d04
Timestamp Timestamp [UCT] Age [y:d:h:m:s] Block Fee (per_kB) Tx size Tx version No of confirmations RingCT/type
1549880320 2019-02-11 10:18:40 00:194:08:26:51 118603 0.0000000000 (0.0000000000) 0.1377 kB 1 139627 no
Extra: 01a5c2d8205a98f3866e4eb8d4dc66ba069a8b1285b3139ef7ac12ca006c968d04021100000001e4839600000000000000000000

2 output(s) for total of 60.0200000000 cash and no token(s)

stealth address amount amount idx token
00: 0f522c9181231988075956b87e14786a02780119762b5956aae2b11a4e9ab054 0.0200000000 26999 of 54738 false
01: 09b0a45ec45d0110271138180e8a3570794a49254b2cf5d437f94a3501c24f44 60.0000000000 120545 of 262588 false

Check which outputs belong to given Safex address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
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 Safex cash or token in this transaction

Tx private key can be obtained using get_tx_key command in safex-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{ "version": 1, "unlock_time": 118663, "vin": [ { "gen": { "height": 118603 } } ], "vout": [ { "amount": 200000000, "token_amount": 0, "target": { "key": "0f522c9181231988075956b87e14786a02780119762b5956aae2b11a4e9ab054" } }, { "amount": 600000000000, "token_amount": 0, "target": { "key": "09b0a45ec45d0110271138180e8a3570794a49254b2cf5d437f94a3501c24f44" } } ], "extra": [ 1, 165, 194, 216, 32, 90, 152, 243, 134, 110, 78, 184, 212, 220, 102, 186, 6, 154, 139, 18, 133, 179, 19, 158, 247, 172, 18, 202, 0, 108, 150, 141, 4, 2, 17, 0, 0, 0, 1, 228, 131, 150, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "signatures": [ ] }


Less details