Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 7cf8732a081aa042426d1f0586e120d6f3a4ddd66599342fbefc363bc2fde405 Tx public key: 7a66f47b5e6a6f54dc0b3ae647b86701223c02f92232f08ef466500a9d5e03ae Payment id (encrypted): 01a6945abe3be816
Timestamp: 1617913606 Timestamp [UCT]: 2021-04-08 20:26:46 Age [y:d:h:m:s]: 00:005:02:51:39
Block: 673298 Fee (per_kB): 1.26 (0.10) Tx size: 13.1797 kB
Tx version: 2 No of confirmations: 3676 RingCT/type: yes/3
Extra: 017a66f47b5e6a6f54dc0b3ae647b86701223c02f92232f08ef466500a9d5e03ae02090101a6945abe3be816

2 output(s) for total of ? upx

stealth address amount amount idx
00: dd7384f45b7d2075ac2f28516c75826aa1e0ddbfbd0b09306b120d3e5477bf4d ? 3352765 of 3370837
01: 7cfd5be35ebf4bcc264ddebff84921021aed666ecc9b65dc84b83c4417578a87 ? 3352766 of 3370837

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: