Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 18293dd574742a9b8f54fa92d643431e6c2fea2976a908014550d75b5597b2e1 Tx public key: 470e357b99a5d9eab5ad2c94a792eb2847405e7bca6e2b492a3fe40eb7b1c350 Payment id (encrypted): 99ed32d4eeec78c3
Timestamp: 1637837932 Timestamp [UCT]: 2021-11-25 10:58:52 Age [y:d:h:m:s]: 00:009:06:49:50
Block: 839366 Fee (per_kB): 0.08 (0.04) Tx size: 1.8340 kB
Tx version: 2 No of confirmations: 6688 RingCT/type: yes/3
Extra: 01470e357b99a5d9eab5ad2c94a792eb2847405e7bca6e2b492a3fe40eb7b1c35002090199ed32d4eeec78c3

2 output(s) for total of ? upx

stealth address amount amount idx
00: 98e000031c0fc3d4f40bc04990c5c3b39688ac89a059f8541b3dd50056611a44 ? 4113840 of 4136453
01: 5b4c10c04a89bc4aa17e094220cbc4cf64998c8646e27b7efe1eda985e1b3b04 ? 4113841 of 4136453

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