Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: d810a3d6fd96cab36e1ffe81509cfa45ea93245cd50cdedcb8e3a7d24ff2f031 Tx public key: f29a9902ad718f0b0cefbba64bff8ef56e946d914133b7047315b6c6a60df6c5
Timestamp: 1637838282 Timestamp [UCT]: 2021-11-25 11:04:42 Age [y:d:h:m:s]: 00:009:04:56:00
Block: 839370 Fee (per_kB): 0.08 (0.04) Tx size: 1.8242 kB
Tx version: 2 No of confirmations: 6634 RingCT/type: yes/3
Extra: 01f29a9902ad718f0b0cefbba64bff8ef56e946d914133b7047315b6c6a60df6c5

2 output(s) for total of ? upx

stealth address amount amount idx
00: 5f90324542f35f6ba2db5ee62f98bb4010ff1d381d3a514a302d25ccb215d94a ? 4113856 of 4136286
01: d1c098d4ca42ee696641c55bb82ad2d71f2ed45fa9a27f3c58555c1a51c8c0ed ? 4113857 of 4136286

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