Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 2e91425f036c93e6c3c7bd5f72dc07c4f92e2295007575e8be2a0145d20bd67e Tx public key: 94a92ac2f96173c9138b448b4d08eaca2b6748eb647d63a694134bfe41515a13 Payment id (encrypted): 86d82a9be5deabf0
Timestamp: 1674618090 Timestamp [UCT]: 2023-01-25 03:41:30 Age [y:d:h:m:s]: 00:007:12:49:03
Block: 1145723 Fee (per_kB): 0.28 (0.04) Tx size: 6.6914 kB
Tx version: 2 No of confirmations: 5426 RingCT/type: yes/3
Extra: 0194a92ac2f96173c9138b448b4d08eaca2b6748eb647d63a694134bfe41515a1302090186d82a9be5deabf0

2 output(s) for total of ? upx

stealth address amount amount idx
00: 6a272865145ae78a61dc175fb5a1d19c2b28249c2a4ccdcecaebd789f8c84161 ? 5267213 of 5284555
01: 359e3d6bfb0b46f4e00b15008993702120faba651d777e6dc7fa834c23bc8360 ? 5267214 of 5284555

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: