Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 9dd5735da56c5aa21775d412cf18e3cf0a594131c0e45966f33c2d91d890a9de Tx public key: 737769036eeb5e1b9cd526606cfa835ebeff6e80f2306f51be68445c289da9af Payment id (encrypted): d116b525359f3451
Timestamp: 1617856375 Timestamp [UCT]: 2021-04-08 04:32:55 Age [y:d:h:m:s]: 00:005:18:39:31
Block: 672815 Fee (per_kB): 0.12 (0.05) Tx size: 2.6445 kB
Tx version: 2 No of confirmations: 4155 RingCT/type: yes/3
Extra: 01737769036eeb5e1b9cd526606cfa835ebeff6e80f2306f51be68445c289da9af020901d116b525359f3451

2 output(s) for total of ? upx

stealth address amount amount idx
00: 95d984b95aa5dc78a277bda6899a74e060bf38a92b6d8f3aae73844e0d0b9622 ? 3341799 of 3370829
01: fbe9672b8f35ade8f69bab061d42b2f2fed477a1ed6ae4fc9bb27e68e19b59e6 ? 3341800 of 3370829

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: