Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 691a4b4dd6c5ed2b9bf33820d076f8b2cbf1385254d39729be63872cd5f86c18 Tx public key: baa33b8eaa01ebb1c2dcf005bafb2711a9a6340326d78488c5b510d6792ebe27 Payment id (encrypted): 0f0079c35c98626e
Timestamp: 1674618090 Timestamp [UCT]: 2023-01-25 03:41:30 Age [y:d:h:m:s]: 00:007:12:21:53
Block: 1145723 Fee (per_kB): 0.12 (0.05) Tx size: 2.6465 kB
Tx version: 2 No of confirmations: 5420 RingCT/type: yes/3
Extra: 01baa33b8eaa01ebb1c2dcf005bafb2711a9a6340326d78488c5b510d6792ebe270209010f0079c35c98626e

2 output(s) for total of ? upx

stealth address amount amount idx
00: fe9c98291d8a20c047c047b15a0f8e6e6d88c005db3ce4c436f193e99f1b34a9 ? 5267209 of 5284542
01: d4a09f7d4734aca43b6341e199063db328bc115e5ad515a5a3e2341855d23c8a ? 5267210 of 5284542

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