Uplexa Block Explorer

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


Autorefresh is OFF
Tx hash: 53ec439df41c8167ce86cc3e3dd9c64b54b8310c4eb980bbe412923941320e21 Tx public key: f0fde7ab0dcb29f0ab65c61f556b488f2d2ad0e56fb63717d04f16308a08320d Payment id (encrypted): 4600df7335d9453d
Timestamp: 1637839800 Timestamp [UCT]: 2021-11-25 11:30:00 Age [y:d:h:m:s]: 00:009:06:18:42
Block: 839378 Fee (per_kB): 0.12 (0.05) Tx size: 2.6465 kB
Tx version: 2 No of confirmations: 6675 RingCT/type: yes/3
Extra: 01f0fde7ab0dcb29f0ab65c61f556b488f2d2ad0e56fb63717d04f16308a08320d0209014600df7335d9453d

2 output(s) for total of ? upx

stealth address amount amount idx
00: 08d7dded8624b7e2d2ead34fdeacc28ef40c9afeb6176ecc0ea727efdc6c0f3a ? 4113893 of 4136452
01: 915836203ac60c8f552d04287a51ac0084f8e58559956a75e45654d4e6a4f07e ? 4113894 of 4136452

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: