Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: da3b49a2af73895235715f84580117183984f41d430512e46de8e624e8f50d77 Tx public key: 6d8bae26b3fb4dbe95e909c54a03a6a3bde88bd7b895a6160f0108c25441feaa Payment id (encrypted): 47fa7c419793262b
Timestamp: 1642190017 Timestamp [UCT]: 2022-01-14 19:53:37 Age [y:d:h:m:s]: 00:013:22:39:46
Block: 875599 Fee (per_kB): 0.08 (0.04) Tx size: 1.8350 kB
Tx version: 2 No of confirmations: 10042 RingCT/type: yes/3
Extra: 016d8bae26b3fb4dbe95e909c54a03a6a3bde88bd7b895a6160f0108c25441feaa02090147fa7c419793262b

2 output(s) for total of ? upx

stealth address amount amount idx
00: 8a6dfa9d4d35eb9385b1f537748b7456c86cfd69eeb5df78de0afe63c57d259a ? 4243800 of 4286513
01: 4c7094c8aa6d7739741b6e78dacd76983d01b4af90ff5c1290b0e5da34c586fe ? 4243801 of 4286513

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: