Tx hash: 42e5b25ab10557fa1f93042e8983cd3049fe81ab3accee078d7cb685319cc682

Tx prefix hash: 42e5b25ab10557fa1f93042e8983cd3049fe81ab3accee078d7cb685319cc682
Tx public key: 82658bccaebe508776a4f126bbdcf0ae23dacc14326b031f0743dc2de95ecedc
Timestamp Timestamp [UCT] Age [y:d:h:m:s] Block Fee (per_kB) Tx size Tx version No of confirmations RingCT/type
1570636947 2019-10-09 16:02:27 00:011:18:17:24 291216 0.0000000000 (0.0000000000) 0.1396 kB 1 8405 no
Extra: 0182658bccaebe508776a4f126bbdcf0ae23dacc14326b031f0743dc2de95ecedc02110000006d58eaea00000000000000000000

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

stealth address amount amount idx token
00: 6bf2cd8e5d952f0a5e3cc8a4d5b635ace4eda6c7ed881531ee092a18834511e9 30.0000000000 56442 of 66087 false
01: 5ad43fcdc1eedb2ba08fa234cbe45f0211136dc0e205b54ce77c81d2517aeccf 100.0000000000 48628 of 59272 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": 291276, "vin": [ { "gen": { "height": 291216 } } ], "vout": [ { "amount": 300000000000, "token_amount": 0, "target": { "key": "6bf2cd8e5d952f0a5e3cc8a4d5b635ace4eda6c7ed881531ee092a18834511e9" } }, { "amount": 1000000000000, "token_amount": 0, "target": { "key": "5ad43fcdc1eedb2ba08fa234cbe45f0211136dc0e205b54ce77c81d2517aeccf" } } ], "extra": [ 1, 130, 101, 139, 204, 174, 190, 80, 135, 118, 164, 241, 38, 187, 220, 240, 174, 35, 218, 204, 20, 50, 107, 3, 31, 7, 67, 220, 45, 233, 94, 206, 220, 2, 17, 0, 0, 0, 109, 88, 234, 234, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "signatures": [ ] }


Less details