Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 674052ac38dbcdf962cf6ee89a34f3302c3cd2e0bcea470d4040af916621e15b Tx public key: a13d3199b531ae8ea3b565d776a76bbbc35743a1910c2b0aa48ffc789d4189cf Payment id (encrypted): 986534cc73ddd299
Timestamp: 1663896422 Timestamp [UCT]: 2022-09-23 01:27:02 Age [y:d:h:m:s]: 01:011:08:33:32
Block: 1056474 Fee (per_kB): 0.08 (0.04) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 270719 RingCT/type: yes/3
Extra: 01a13d3199b531ae8ea3b565d776a76bbbc35743a1910c2b0aa48ffc789d4189cf020901986534cc73ddd299

2 output(s) for total of ? upx

stealth address amount amount idx
00: 0e8051f4c7925348495dc0af104c1612b79d1ad622efc1b238f28846e5061da5 ? 4979697 of 5802117
01: f108a4748debd08d310f4b1ed5a456ea5542f67c9164ca434173c0faf6040c20 ? 4979698 of 5802117

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: