Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: b5567994752570301120b3e85438fcba350fa308afdf30177e4dcf913549ae36 Tx public key: 73be29c677d57b96f10f841b5a1d3c53ae2e967a2da119b334f8809db115643f Payment id (encrypted): d7fa32f0dcdef914
Timestamp: 1617917675 Timestamp [UCT]: 2021-04-08 21:34:35 Age [y:d:h:m:s]: 00:005:01:54:30
Block: 673330 Fee (per_kB): 0.08 (0.04) Tx size: 1.8359 kB
Tx version: 2 No of confirmations: 3650 RingCT/type: yes/3
Extra: 0173be29c677d57b96f10f841b5a1d3c53ae2e967a2da119b334f8809db115643f020901d7fa32f0dcdef914

2 output(s) for total of ? upx

stealth address amount amount idx
00: 0e6306cdad9bcd595f39a37ca7d8b5a643e4e04421ae68c6c17d2b12cca60b8e ? 3352942 of 3370880
01: e4bac86bf57f18d5693f635bd53a5c24e606b047c4b8f040310dd3469ef25127 ? 3352943 of 3370880

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: