Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: f5275bc604a5430a9f92c42da2b2e964a2964a97f408c8361f9a1c79561bd660 Tx public key: fb497027666d4d093629675fc95b6563e3761fea4be3de3c1821da35301709ff Payment id (encrypted): f7704b0f4fb551f0
Timestamp: 1695327381 Timestamp [UCT]: 2023-09-21 20:16:21 Age [y:d:h:m:s]: 00:072:22:08:13
Block: 1318122 Fee (per_kB): 0.12 (0.05) Tx size: 2.6426 kB
Tx version: 2 No of confirmations: 52472 RingCT/type: yes/3
Extra: 01fb497027666d4d093629675fc95b6563e3761fea4be3de3c1821da35301709ff020901f7704b0f4fb551f0

2 output(s) for total of ? upx

stealth address amount amount idx
00: a9334a678b308569eeb7d0f40f75244aaa3bbeb2ef56c154c6828e421df4b1c2 ? 5773579 of 5948429
01: d66da025ae0e1ff2b06b30b961c282b492a8c4e79688bf24a3e08f6ad8bcf397 ? 5773580 of 5948429

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