Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: df12e19b9fc6f2b91061b0d85a41831936238fa03216de9b0c11dd53bbc2cfdd Tx public key: af1642a567c68a76c61dbbf3c900219894b3bf3692cedaac803dea2fa4906ce1 Payment id (encrypted): 853f6d1e6ade8691
Timestamp: 1620124668 Timestamp [UCT]: 2021-05-04 10:37:48 Age [y:d:h:m:s]: 00:006:13:40:38
Block: 691750 Fee (per_kB): 2.50 (1.35) Tx size: 1.8457 kB
Tx version: 2 No of confirmations: 4741 RingCT/type: yes/3
Extra: 020901853f6d1e6ade869101af1642a567c68a76c61dbbf3c900219894b3bf3692cedaac803dea2fa4906ce1

2 output(s) for total of ? upx

stealth address amount amount idx
00: ad6ee397973a034f08b6b3d8ae383d3d261751caf938190f00c9f8a52e6f98e7 ? 3461156 of 3489580
01: 6000a3b0fe39d7c5b595e73ab1fcf74854036ed8953d73f54ab510fba56347f8 ? 3461157 of 3489580

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