Tx hash: c4e549fd1ce4fb5ad244b8526bc568d9a99c04ff0630517f23530da35305b8cc

Tx prefix hash: c4e549fd1ce4fb5ad244b8526bc568d9a99c04ff0630517f23530da35305b8cc
Tx public key: 406eeabd91db88590f6ecd1f4c8fd3667bdc9c343febec52d6324bf9aaa86ef4
Timestamp Timestamp [UCT] Age [y:d:h:m:s] Block Fee (per_kB) Tx size Tx version No of confirmations RingCT/type
1573226727 2019-11-08 15:25:27 00:013:18:52:20 312713 0.0000000000 (0.0000000000) 0.1357 kB 1 9882 no
Extra: 01406eeabd91db88590f6ecd1f4c8fd3667bdc9c343febec52d6324bf9aaa86ef4020d39303031000300000004581cbb

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

stealth address amount amount idx token
00: 318ce5b34be166da9a1654cba343a9ff0a6a02051bd34b2810f8dc34ec533869 30.0000000000 80319 of 90625 false
01: dbda3f8b108f3ac8844cf3b739461b771216319a9b7c9159774291f3f1dfd411 100.0000000000 75283 of 86013 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": 312773, "vin": [ { "gen": { "height": 312713 } } ], "vout": [ { "amount": 300000000000, "token_amount": 0, "target": { "key": "318ce5b34be166da9a1654cba343a9ff0a6a02051bd34b2810f8dc34ec533869" } }, { "amount": 1000000000000, "token_amount": 0, "target": { "key": "dbda3f8b108f3ac8844cf3b739461b771216319a9b7c9159774291f3f1dfd411" } } ], "extra": [ 1, 64, 110, 234, 189, 145, 219, 136, 89, 15, 110, 205, 31, 76, 143, 211, 102, 123, 220, 156, 52, 63, 235, 236, 82, 214, 50, 75, 249, 170, 168, 110, 244, 2, 13, 57, 48, 48, 49, 0, 3, 0, 0, 0, 4, 88, 28, 187 ], "signatures": [ ] }


Less details