Tx hash: 79e672d8680273f9e7aec3d733e85b454f43546bdf4fc988cbdccd61d5e190e3

Tx prefix hash: 79e672d8680273f9e7aec3d733e85b454f43546bdf4fc988cbdccd61d5e190e3
Tx public key: 3b23a4e7263510346a222db1c6879e32d3b319fcac5ea39279fb8d6c3ed6eea9
Timestamp Timestamp [UCT] Age [y:d:h:m:s] Block Fee (per_kB) Tx size Tx version No of confirmations RingCT/type
1549880214 2019-02-11 10:16:54 00:073:04:34:18 118600 0.0000000000 (0.0000000000) 0.1348 kB 1 52562 no
Extra: 013b23a4e7263510346a222db1c6879e32d3b319fcac5ea39279fb8d6c3ed6eea9020d3930303100080000002d4f4df6

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

stealth address amount amount idx token
00: d90ab991399844ae57b7008dc2dc5ee7b34696627a9064de9df8784505427bed 0.0600000000 43968 of 50995 false
01: e7c8d8926133a9b7d9f344eff7a93dc062863aa9d858709c76246c9e4528200d 60.0000000000 120542 of 173768 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": 118660, "vin": [ { "gen": { "height": 118600 } } ], "vout": [ { "amount": 600000000, "token_amount": 0, "target": { "key": "d90ab991399844ae57b7008dc2dc5ee7b34696627a9064de9df8784505427bed" } }, { "amount": 600000000000, "token_amount": 0, "target": { "key": "e7c8d8926133a9b7d9f344eff7a93dc062863aa9d858709c76246c9e4528200d" } } ], "extra": [ 1, 59, 35, 164, 231, 38, 53, 16, 52, 106, 34, 45, 177, 198, 135, 158, 50, 211, 179, 25, 252, 172, 94, 163, 146, 121, 251, 141, 108, 62, 214, 238, 169, 2, 13, 57, 48, 48, 49, 0, 8, 0, 0, 0, 45, 79, 77, 246 ], "signatures": [ ] }


Less details