Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 10e81273bfaaf3e6e20e4699e0d647d4e7a6cdb29aa0eae9eee9ed7485eecc2d Tx public key: 1b245cdd8401286d370f0bc541d51a5f5ffb98557d70505410dc0a97e7d46c77
Timestamp: 1679175660 Timestamp [UCT]: 2023-03-18 21:41:00 Age [y:d:h:m:s]: 00:012:11:37:33
Block: 1183691 Fee (per_kB): 0.48 (0.04) Tx size: 11.5264 kB
Tx version: 2 No of confirmations: 8985 RingCT/type: yes/3
Extra: 011b245cdd8401286d370f0bc541d51a5f5ffb98557d70505410dc0a97e7d46c77

2 output(s) for total of ? upx

stealth address amount amount idx
00: 91a6e11c83b16fa3efe764d1d11ab072532d5ca7fd66bdc4d4d22fef5a17d3db ? 5382908 of 5411140
01: d463cd4c7402637774a995eef71f4792f547aa46b6a5bc4a95ed8aba42c08719 ? 5382909 of 5411140

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