Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 4f5fb26e88c8e8fd427e04b1a0046093fa50a429c2c73714d6a790c004387edb Tx public key: 9da71d02537404f7b3f7af0d0c3f8c97e5f0b997c7d026ab98f8c56f43c5e264
Timestamp: 1663898318 Timestamp [UCT]: 2022-09-23 01:58:38 Age [y:d:h:m:s]: 00:013:02:07:55
Block: 1056482 Fee (per_kB): 0.48 (0.04) Tx size: 11.5332 kB
Tx version: 2 No of confirmations: 9402 RingCT/type: yes/3
Extra: 019da71d02537404f7b3f7af0d0c3f8c97e5f0b997c7d026ab98f8c56f43c5e264

2 output(s) for total of ? upx

stealth address amount amount idx
00: bf6e59598e6a7e6a469b94ca1f94ec8b215c5c08c9dc7f975eb339e6e1a357b4 ? 4979720 of 5013525
01: a61cffb7213f616fc1e36997a57ef00002611fdba94ee224552d09116bb53527 ? 4979721 of 5013525

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: