Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 8047affde9b79fe4f2ba7ac5ef50217cf2379d97c9e47c4c40eb005fb8a0a840 Tx public key: 8f9fa13503814594e9ad942a8dbf3f8f11e34a355874a934934fd56676cb9134 Payment id (encrypted): 4cc0d79bc26bf999
Timestamp: 1663896422 Timestamp [UCT]: 2022-09-23 01:27:02 Age [y:d:h:m:s]: 01:011:09:03:33
Block: 1056474 Fee (per_kB): 0.08 (0.04) Tx size: 1.8389 kB
Tx version: 2 No of confirmations: 270733 RingCT/type: yes/3
Extra: 018f9fa13503814594e9ad942a8dbf3f8f11e34a355874a934934fd56676cb91340209014cc0d79bc26bf999

2 output(s) for total of ? upx

stealth address amount amount idx
00: 1605f80de9eca64fc719669333b63fe5a502d5afb2e0c74e5bd4301a6a4bab4b ? 4979699 of 5802149
01: dc16b7d7afeeddeb23021407602dbdcb3832bbcec716656bdc71b74b5ddc8ec1 ? 4979700 of 5802149

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: