Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 4a1231bc548314d5b297a302a95e84c6d3948ea0ca39be796b1224d645dc815a Tx public key: ffa70aef9c3e9fd74fc0fd1c8f66aae28d3d1205ac454499cf22385cf672430d
Timestamp: 1659815083 Timestamp [UCT]: 2022-08-06 19:44:43 Age [y:d:h:m:s]: 00:011:14:54:53
Block: 1022436 Fee (per_kB): 0.08 (0.04) Tx size: 1.8223 kB
Tx version: 2 No of confirmations: 8368 RingCT/type: yes/3
Extra: 01ffa70aef9c3e9fd74fc0fd1c8f66aae28d3d1205ac454499cf22385cf672430d

2 output(s) for total of ? upx

stealth address amount amount idx
00: 1c38cb8cb16d7ab2e77aa4b7a4e71144839a350f932162d4f8724e3089f2ccb9 ? 4856688 of 4890257
01: c8fdd9f1b1bb4531663cbb7af9c1ae1049dbf249f022513431f25dcc2d95a589 ? 4856689 of 4890257

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