Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 4d2ac8bdbcd56a60da4919ecfbed66cf56fbe306540d2b3bc668493500cda67c Tx public key: 639f3e92007b988255e2a3c6018bfe517fcb31be0bb6403351caab048019c2d7 Payment id (encrypted): 92dd2dc4bfcaedea
Timestamp: 1659747112 Timestamp [UCT]: 2022-08-06 00:51:52 Age [y:d:h:m:s]: 00:012:10:38:43
Block: 1021871 Fee (per_kB): 0.56 (0.04) Tx size: 13.1582 kB
Tx version: 2 No of confirmations: 8952 RingCT/type: yes/3
Extra: 02090192dd2dc4bfcaedea01639f3e92007b988255e2a3c6018bfe517fcb31be0bb6403351caab048019c2d7

2 output(s) for total of ? upx

stealth address amount amount idx
00: 47f3adb5479a4fce8d9148312274eb01067dd778ec568768db8b7fecd4daaf2e ? 4854874 of 4890320
01: 3db35729ae548e0108573bc89deaf00487fb517309c17014427819388bdc0c5e ? 4854875 of 4890320

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