Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 9168fac795f83872e3c78068521cb97d0e81863cdff835573fb7ebb61fc7ab42 Tx public key: 96e8d74c85fb26b6c5ed3bbc7902d46c94e6c158c534e84f57a4454fe1c98bfd Payment id (encrypted): 22ad8f690061a80c
Timestamp: 1663966478 Timestamp [UCT]: 2022-09-23 20:54:38 Age [y:d:h:m:s]: 00:012:07:35:55
Block: 1057054 Fee (per_kB): 0.24 (0.05) Tx size: 5.0723 kB
Tx version: 2 No of confirmations: 8845 RingCT/type: yes/3
Extra: 0196e8d74c85fb26b6c5ed3bbc7902d46c94e6c158c534e84f57a4454fe1c98bfd02090122ad8f690061a80c

2 output(s) for total of ? upx

stealth address amount amount idx
00: 7c77dd09ff43979626c1cdf7abe25b3e2a2475bcbbd54f22c418387b91643856 ? 4981728 of 5013597
01: 9d3f361c1c96d902d7319cf6f0bd6d8a36f6eb078c22a0445bdfd9a6bd9cd82a ? 4981729 of 5013597

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: