Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 6f0aeb9b9d7f65161b29b28cc46614ba53ff986c428041b9244bae0f5b4b2e41 Tx public key: 5cff0909ea0c8fb5b1a1637abf968078951c01c4f394ab05817417badf41f821 Payment id (encrypted): e6cae2b62e11c9e9
Timestamp: 1620125439 Timestamp [UCT]: 2021-05-04 10:50:39 Age [y:d:h:m:s]: 00:006:13:30:48
Block: 691755 Fee (per_kB): 2.50 (0.25) Tx size: 10.0029 kB
Tx version: 2 No of confirmations: 4739 RingCT/type: yes/3
Extra: 020901e6cae2b62e11c9e9015cff0909ea0c8fb5b1a1637abf968078951c01c4f394ab05817417badf41f821

2 output(s) for total of ? upx

stealth address amount amount idx
00: e9704a758ca43fbc7c6be12e3f201a2370f286056b9f1ad8114de8532ccf2a78 ? 3461218 of 3489593
01: 7275c125fd73ac365e107cdb1d6250194a82827770be382915ff950e802f5993 ? 3461219 of 3489593

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: