Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 8679d1bdbbc73ffd98ea03f734930a8ccc031728e98639ba778001ef7e4dffbc Tx public key: 9893424c272e0edc2894a0ff4ea667efbbf1a5d501f2b1ae4f7ff5bd871c4a89
Timestamp: 1623361505 Timestamp [UCT]: 2021-06-10 21:45:05 Age [y:d:h:m:s]: 00:008:17:30:22
Block: 718720 Fee (per_kB): 0.12 (0.05) Tx size: 2.6318 kB
Tx version: 2 No of confirmations: 6293 RingCT/type: yes/3
Extra: 019893424c272e0edc2894a0ff4ea667efbbf1a5d501f2b1ae4f7ff5bd871c4a89

2 output(s) for total of ? upx

stealth address amount amount idx
00: 848f897ede3d39aa4da99b0ab5c063a6064ab19ba59c25639eafd5c1c2a68519 ? 3613512 of 3646026
01: 8d36c983d2a8178ad3e20f2a01793c715721ccb89aed05b962b634ac5156f3a4 ? 3613513 of 3646026

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