Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: f9984aea5dc5ecb86de48e87d290f76d28bba3720cc5708ee5ffa87315850785 Tx public key: fac58986c284b0347d841cbafaf8fef8e081051389be03c3ba3e79d7e5e832a2 Payment id (encrypted): 277a3a35418cb0c3
Timestamp: 1620126338 Timestamp [UCT]: 2021-05-04 11:05:38 Age [y:d:h:m:s]: 00:006:14:06:53
Block: 691762 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 4751 RingCT/type: yes/3
Extra: 01fac58986c284b0347d841cbafaf8fef8e081051389be03c3ba3e79d7e5e832a2020901277a3a35418cb0c3

2 output(s) for total of ? upx

stealth address amount amount idx
00: 189a1d70965b84db6d2ca5b36fc539bdcee2e50820f43315125eecacc67509ec ? 3461267 of 3489712
01: 8fe8a74a4d0b3724859973b6db1424e1788963e8dea087d018d6b5a880443db1 ? 3461268 of 3489712

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: