Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 1690c63aa08b3d6c2d843d1e718ae78c8784597b0e6673a352f8dc7595f82059 Tx public key: 544d554b968b1996f7d03ef507d4f6ff6b876d7dffb156afd5eaf4ca40a10616
Timestamp: 1679176877 Timestamp [UCT]: 2023-03-18 22:01:17 Age [y:d:h:m:s]: 00:012:11:11:24
Block: 1183697 Fee (per_kB): 0.00 (0.00) Tx size: 0.1318 kB
Tx version: 2 No of confirmations: 8979 RingCT/type: yes/0
Extra: 01544d554b968b1996f7d03ef507d4f6ff6b876d7dffb156afd5eaf4ca40a106160211000000029f2e755e000000000000000000032100ac3ad949a7a76ccee32b86154c49470d3d011c2bfc7d6ad342c0af541fe773fa

1 output(s) for total of 1656.76 upx

stealth address amount amount idx
00: 4b3094eed471887f598a8d8aed192265915d095d6c90c9c9e7395a1cd9786097 1656.76 5382928 of 0

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