Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: bc97c54f06636e30572a724b284b65928213d7828f07a2f013a81d8941f9df28 Tx public key: 171bc7341238ba0bc8214db21b597500c8feca1e7d9c4ce618db2a95c7d09fbb Payment id (encrypted): b469ad18deeeec7c
Timestamp: 1620124668 Timestamp [UCT]: 2021-05-04 10:37:48 Age [y:d:h:m:s]: 00:006:13:37:40
Block: 691750 Fee (per_kB): 0.32 (0.17) Tx size: 1.8369 kB
Tx version: 2 No of confirmations: 4741 RingCT/type: yes/3
Extra: 01171bc7341238ba0bc8214db21b597500c8feca1e7d9c4ce618db2a95c7d09fbb020901b469ad18deeeec7c

2 output(s) for total of ? upx

stealth address amount amount idx
00: 064f227cd034f3a66f16b45faaaba8657c704795f117607bc2d2a3700d07f150 ? 3461166 of 3489580
01: a0c62bdc43fc07f79f34a0c5aa0ee790039b7dc6ee0ec7aa7022c7e91aa7e28c ? 3461167 of 3489580

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