Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 9795281d006f54c7e7dcdd3b6699de98d66a16254a4ccb9240d5213b2252499a Tx public key: a8db6da790fcf56844bd2d921c1d8b6a9edf45ae825fb37beec97e34efd727b0 Payment id (encrypted): ddef94661af91fb0
Timestamp: 1659747112 Timestamp [UCT]: 2022-08-06 00:51:52 Age [y:d:h:m:s]: 00:012:10:38:31
Block: 1021871 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 8951 RingCT/type: yes/3
Extra: 020901ddef94661af91fb001a8db6da790fcf56844bd2d921c1d8b6a9edf45ae825fb37beec97e34efd727b0

2 output(s) for total of ? upx

stealth address amount amount idx
00: 161939d40afc5c70f0ce46dbfed38d6695af62e0ccc56919c99738885395243d ? 4854872 of 4890311
01: c92c2b76bec2d6c56051c8dbae1165c61b93dbf81005d60182c49fb704f7953c ? 4854873 of 4890311

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: 0.2.2.0-45887ac92