Tx hash: d69ace4c62b711a227002a9a20713feeeea8c66ffbc90a6901b3439660cad4e5

Tx prefix hash: d69ace4c62b711a227002a9a20713feeeea8c66ffbc90a6901b3439660cad4e5
Tx public key: 8a14ce267426e9ed0012759de527e08432fdc55ec12d94581a2ae340c3be668e
Timestamp Timestamp [UCT] Age [y:d:h:m:s] Block Fee (per_kB) Tx size Tx version No of confirmations RingCT/type
1570637747 2019-10-09 16:15:47 00:011:18:24:24 291222 0.0000000000 (0.0000000000) 0.1396 kB 1 8413 no
Extra: 018a14ce267426e9ed0012759de527e08432fdc55ec12d94581a2ae340c3be668e0211000000eb94a83e00000000000000000000

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

stealth address amount amount idx token
00: e645f533ef216d069c4890540b7edee9e5ad1c128b55f15952b42aef9149e06a 30.0000000000 56448 of 66103 false
01: cc65efe5d807528928d91b8da1eab881425b4a7029af903094bb911ab7fffcde 100.0000000000 48637 of 59288 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": 291282, "vin": [ { "gen": { "height": 291222 } } ], "vout": [ { "amount": 300000000000, "token_amount": 0, "target": { "key": "e645f533ef216d069c4890540b7edee9e5ad1c128b55f15952b42aef9149e06a" } }, { "amount": 1000000000000, "token_amount": 0, "target": { "key": "cc65efe5d807528928d91b8da1eab881425b4a7029af903094bb911ab7fffcde" } } ], "extra": [ 1, 138, 20, 206, 38, 116, 38, 233, 237, 0, 18, 117, 157, 229, 39, 224, 132, 50, 253, 197, 94, 193, 45, 148, 88, 26, 42, 227, 64, 195, 190, 102, 142, 2, 17, 0, 0, 0, 235, 148, 168, 62, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "signatures": [ ] }


Less details