Uplexa Block Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)


Autorefresh is OFF
Tx hash: a45ed6c3d965aa6c79c0fd5c3fdbeac88baa9714606926b0e1329be8a5d020f7 Tx public key: c6856239f6da00290cc343ad380bd484bca5bc60d3f91b6f7a85e4f612b52be8 Payment id (encrypted): 522e1331c59a4a86
Timestamp: 1620124827 Timestamp [UCT]: 2021-05-04 10:40:27 Age [y:d:h:m:s]: 00:006:13:44:01
Block: 691752 Fee (per_kB): 1.26 (0.10) Tx size: 13.1914 kB
Tx version: 2 No of confirmations: 4743 RingCT/type: yes/3
Extra: 01c6856239f6da00290cc343ad380bd484bca5bc60d3f91b6f7a85e4f612b52be8020901522e1331c59a4a86

2 output(s) for total of ? upx

stealth address amount amount idx
00: 5ea68cd399bc4c89a38def6eb2612f2f5b7394810b64b65012f023b61755f6e3 ? 3461208 of 3489594
01: ef8c9d7582fbc052058d3bb3b1f1b3d83d0e44de60e6701125811eb8398fd186 ? 3461209 of 3489594

Check which outputs belong to given uPlexa 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 uPlexa in this transaction

Tx private key can be obtained using get_tx_key command in uplexa-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

source code | explorer version (api): master-2019-01-05-0432f03 (1.1) | uPlexa version: