Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: b1366a46adb9a44b71a3ad1344ec2bb1b541dab4d68a1f4be9ac4fc656e3f10e Tx public key: fb2db322ca808790bf71b846cd7678a41eb69e72588e1ce4d047fef2ef20a1a7 Payment id (encrypted): bd8ff1a20243b988
Timestamp: 1617913606 Timestamp [UCT]: 2021-04-08 20:26:46 Age [y:d:h:m:s]: 00:005:03:18:40
Block: 673298 Fee (per_kB): 1.26 (0.10) Tx size: 13.1816 kB
Tx version: 2 No of confirmations: 3690 RingCT/type: yes/3
Extra: 01fb2db322ca808790bf71b846cd7678a41eb69e72588e1ce4d047fef2ef20a1a7020901bd8ff1a20243b988

2 output(s) for total of ? upx

stealth address amount amount idx
00: 46152d1c97282134fc8e8756182bfb88e5bf2d284b76ef500ee199c8ecad33ae ? 3352769 of 3370907
01: 9c8ffc318f1e36b88fec9c8856563b00ca85fdea976571e1f6d2b3e8b2e95223 ? 3352770 of 3370907

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