Tx hash: bb3d220badc683ebe389c9dd2fa479c026fcafd3338cacefca517cf5fa86465a

Tx prefix hash: bb3d220badc683ebe389c9dd2fa479c026fcafd3338cacefca517cf5fa86465a
Tx public key: c20f6ca06122d49b4359d0e44d33da5f22d9b791e2a08b6c2e7aad73ccd17bb3
Timestamp Timestamp [UCT] Age [y:d:h:m:s] Block Fee (per_kB) Tx size Tx version No of confirmations RingCT/type
1560327876 2019-06-12 08:24:36 00:007:03:32:47 205446 0.0000000000 (0.0000000000) 0.1348 kB 1 5151 no
Extra: 01c20f6ca06122d49b4359d0e44d33da5f22d9b791e2a08b6c2e7aad73ccd17bb3020d393030310008000000117ac571

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

stealth address amount amount idx token
00: d33b58d8dbd2a07b989d7773b07e85db20bee1b36513d05931099b418939ff9a 0.0500000000 34709 of 35390 false
01: b0b4e3732293d40300eaca61f7b37b37369ea782a4f655cfb39e6a4eeed7c4b0 60.0000000000 208807 of 214027 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": 205506, "vin": [ { "gen": { "height": 205446 } } ], "vout": [ { "amount": 500000000, "token_amount": 0, "target": { "key": "d33b58d8dbd2a07b989d7773b07e85db20bee1b36513d05931099b418939ff9a" } }, { "amount": 600000000000, "token_amount": 0, "target": { "key": "b0b4e3732293d40300eaca61f7b37b37369ea782a4f655cfb39e6a4eeed7c4b0" } } ], "extra": [ 1, 194, 15, 108, 160, 97, 34, 212, 155, 67, 89, 208, 228, 77, 51, 218, 95, 34, 217, 183, 145, 226, 160, 139, 108, 46, 122, 173, 115, 204, 209, 123, 179, 2, 13, 57, 48, 48, 49, 0, 8, 0, 0, 0, 17, 122, 197, 113 ], "signatures": [ ] }


Less details