Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 5dcc534522bb445fc94c551e35d887c7b72b787ca7d022f056eeaeea3ea9c5ff Tx public key: c312fbd7321e8aab1757bd9f8c0f471526864a01fd51072f5cb8f5a4e1c352d2
Timestamp: 1669299842 Timestamp [UCT]: 2022-11-24 14:24:02 Age [y:d:h:m:s]: 00:013:18:30:31
Block: 1101449 Fee (per_kB): 0.08 (0.04) Tx size: 1.8232 kB
Tx version: 2 No of confirmations: 9922 RingCT/type: yes/3
Extra: 01c312fbd7321e8aab1757bd9f8c0f471526864a01fd51072f5cb8f5a4e1c352d2

2 output(s) for total of ? upx

stealth address amount amount idx
00: c2e33b6e71825196ce646b1285675f44120b6d779901be63d5a1c9b14dbc4a8e ? 5144455 of 5172100
01: 273a8609590d75b4b6752d1d5d3c181ab964ca558aa45235dd4d54c3e5bea47b ? 5144456 of 5172100

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