Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 0d2a0e181f86b71a6889fa8e121ae4c36e372ebbfd553e5a28738c9d41a1ca0d Tx public key: 0ef685f1cb95a9140eee25f0f452133b98b3efcf8c517e25317337ad2324a7f1 Payment id (encrypted): 142341cd30b561f1
Timestamp: 1617917675 Timestamp [UCT]: 2021-04-08 21:34:35 Age [y:d:h:m:s]: 00:005:01:31:52
Block: 673330 Fee (per_kB): 0.08 (0.04) Tx size: 1.8379 kB
Tx version: 2 No of confirmations: 3637 RingCT/type: yes/3
Extra: 010ef685f1cb95a9140eee25f0f452133b98b3efcf8c517e25317337ad2324a7f1020901142341cd30b561f1

2 output(s) for total of ? upx

stealth address amount amount idx
00: 88953bdcf685a2596c393589522ce0ace6496d06be1a9f08f4db83d58f086fc0 ? 3352944 of 3370814
01: fc1fb6453450e6f3bb5e216ac43f875a0f12c3fa15f349adc642d0833b209f75 ? 3352945 of 3370814

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: 0.2.2.0-45887ac92