Tx hash: 33fd0252a88c0db1cee8eb378bbdda1b1b1efcfb5815a2c774bdb93d0f1b860e

Tx prefix hash: 33fd0252a88c0db1cee8eb378bbdda1b1b1efcfb5815a2c774bdb93d0f1b860e
Tx public key: 5d264b0a38508e02487e219a26013ef41d5118a621f390ace8218e870cd90cd1
Timestamp Timestamp [UCT] Age [y:d:h:m:s] Block Fee (per_kB) Tx size Tx version No of confirmations RingCT/type
1560328001 2019-06-12 08:26:41 00:097:16:43:39 205447 0.0000000000 (0.0000000000) 0.1299 kB 1 70221 no
Extra: 015d264b0a38508e02487e219a26013ef41d5118a621f390ace8218e870cd90cd1020800486c96671a2700

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

stealth address amount amount idx token
00: 5593435fabd1991a181f4f420e225c107a2feb70948e738341fef3c0c923acf3 0.0400000000 37556 of 47957 false
01: e4f0f4f0bb7fd41f4329b28b214757f0d22ce073d992d09f6895cebf245f279c 60.0000000000 208808 of 268870 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": 205507, "vin": [ { "gen": { "height": 205447 } } ], "vout": [ { "amount": 400000000, "token_amount": 0, "target": { "key": "5593435fabd1991a181f4f420e225c107a2feb70948e738341fef3c0c923acf3" } }, { "amount": 600000000000, "token_amount": 0, "target": { "key": "e4f0f4f0bb7fd41f4329b28b214757f0d22ce073d992d09f6895cebf245f279c" } } ], "extra": [ 1, 93, 38, 75, 10, 56, 80, 142, 2, 72, 126, 33, 154, 38, 1, 62, 244, 29, 81, 24, 166, 33, 243, 144, 172, 232, 33, 142, 135, 12, 217, 12, 209, 2, 8, 0, 72, 108, 150, 103, 26, 39, 0 ], "signatures": [ ] }


Less details