Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: b6ca40ac357d1009f432e1a0bb9c73cb7cb4d69b52f0cb1c39a94d7ab66703e1 Tx public key: 278abea3db48f419d9024b280162b1a884e1f5b227abe0ac739bed1b12d49bed Payment id (encrypted): b7d35c40ff04f625
Timestamp: 1663896422 Timestamp [UCT]: 2022-09-23 01:27:02 Age [y:d:h:m:s]: 01:008:00:00:23
Block: 1056474 Fee (per_kB): 0.08 (0.04) Tx size: 1.8330 kB
Tx version: 2 No of confirmations: 268272 RingCT/type: yes/3
Extra: 01278abea3db48f419d9024b280162b1a884e1f5b227abe0ac739bed1b12d49bed020901b7d35c40ff04f625

2 output(s) for total of ? upx

stealth address amount amount idx
00: 71fd69b72688a37c5e7346a7363dfca0658f01445fc6a92d11b99919009feced ? 4979695 of 5794957
01: 52deb09a4625d290cba9b7d63a31a6c70efbc6f8633933c4d7cae6f862e34bf2 ? 4979696 of 5794957

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: