Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 4316a367fce7a3052fbd9c7e1f8a5889ea732b999c3db6540e65355fb3a93eae Tx public key: 3bae18ee1c21f35f1f1eb87c8c441fa6f84c8d484324214abef2f92f4647f33d Payment id (encrypted): d10138be4f0f06e9
Timestamp: 1652529054 Timestamp [UCT]: 2022-05-14 11:50:54 Age [y:d:h:m:s]: 00:008:07:15:42
Block: 961727 Fee (per_kB): 0.08 (0.04) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 5983 RingCT/type: yes/3
Extra: 013bae18ee1c21f35f1f1eb87c8c441fa6f84c8d484324214abef2f92f4647f33d020901d10138be4f0f06e9

2 output(s) for total of ? upx

stealth address amount amount idx
00: fa16596a8761b7841d2b1b5dc394f01590bb65a8a9c5edce7879216bae40008c ? 4592727 of 4617868
01: 180dfff1780eb97df2ad581665167a1acf4d7661bd07e5eeb14ec53d26798585 ? 4592728 of 4617868

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