Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: f0ae2a92c90e6db982beaf8b192105945ad9c6d4a65b08669fd89e0f04d5ea60 Tx public key: 73a1fc2310a13913024f3fb64e5c6bbca85cbb77dbea9b73df301e2cf866754f Payment id (encrypted): 9397d8bae46774ab
Timestamp: 1674619093 Timestamp [UCT]: 2023-01-25 03:58:13 Age [y:d:h:m:s]: 00:007:11:14:21
Block: 1145730 Fee (per_kB): 0.12 (0.05) Tx size: 2.6465 kB
Tx version: 2 No of confirmations: 5396 RingCT/type: yes/3
Extra: 0173a1fc2310a13913024f3fb64e5c6bbca85cbb77dbea9b73df301e2cf866754f0209019397d8bae46774ab

2 output(s) for total of ? upx

stealth address amount amount idx
00: 0ffd18b622f0d012645305daf9d8c85365e5edee17afb695c5dd62186e3c9756 ? 5267236 of 5284482
01: 14b79e7a792160863785994e66e5be9f4fc81322b8231a53dc5fbbea48dc760a ? 5267237 of 5284482

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: