Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 406a6957cbd0f1d176e7dfe0d57210d0521b6c27eb409072f9dc5dbbfc8a6dc5 Tx public key: 7d29b55ad898d6a1384889ac72c89607d67b1b05c5b1437bfc2e4dd981121aa8 Payment id (encrypted): 76c99f79301c4dd6
Timestamp: 1623361853 Timestamp [UCT]: 2021-06-10 21:50:53 Age [y:d:h:m:s]: 00:008:18:27:34
Block: 718724 Fee (per_kB): 0.12 (0.05) Tx size: 2.6416 kB
Tx version: 2 No of confirmations: 6322 RingCT/type: yes/3
Extra: 017d29b55ad898d6a1384889ac72c89607d67b1b05c5b1437bfc2e4dd981121aa802090176c99f79301c4dd6

2 output(s) for total of ? upx

stealth address amount amount idx
00: ef85b8067fad5a1f6ad4412d41819dd2518af00bd7e4e9d600390f9982c919f8 ? 3613559 of 3646184
01: 54d7b54a504355f57735a132b8a460a1b0f01d250b7b27955f2bd77abda61714 ? 3613560 of 3646184

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: