Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 2146d3337f601f1c5237d010e276aaec379b729795ed1d045aa0e3ea5bca7b04 Tx public key: 6f856d8fac82dc6a723f67855a53275de9684f3eee213e4d1ebef5ebf5f67607 Payment id (encrypted): 03a0451e7d759a22
Timestamp: 1546465209 Timestamp [UCT]: 2019-01-02 21:40:09 Age [y:d:h:m:s]: 04:338:00:50:26
Block: 77892 Fee (per_kB): 12.60 (0.96) Tx size: 13.1572 kB
Tx version: 2 No of confirmations: 1294275 RingCT/type: yes/3
Extra: 02090103a0451e7d759a22016f856d8fac82dc6a723f67855a53275de9684f3eee213e4d1ebef5ebf5f67607

2 output(s) for total of ? upx

stealth address amount amount idx
00: 221adc8f9e9c81909047cb8f3086dd9e2f0ad11d257ca22b2daa7a0eb0505709 ? 203890 of 5953903
01: 656119cd464bfa2f6317be1c96a094a7913b401805c4bd68ade486baf4049512 ? 203891 of 5953903

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: