Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 7b7e9268a5590448c1e6ef1c2dce9a10c693e393287dfb64802f3dac6ae1fa99 Tx public key: d875d7e3a46674cc8734dcdce49f079917bd3d9b1592478224eb5d299881c6d9
Timestamp: 1547249633 Timestamp [UCT]: 2019-01-11 23:33:53 Age [y:d:h:m:s]: 04:331:06:59:31
Block: 84478 Fee (per_kB): 7.20 (3.94) Tx size: 1.8271 kB
Tx version: 2 No of confirmations: 1289361 RingCT/type: yes/3
Extra: 01d875d7e3a46674cc8734dcdce49f079917bd3d9b1592478224eb5d299881c6d9

2 output(s) for total of ? upx

stealth address amount amount idx
00: 50ebd3aae926b9e0269f8981b8480c3e1f9f05d62fdeb149680c113aa91be9b9 ? 239299 of 5960212
01: a9b1ca9d62f1eb91aa0b4d2fa6d58896a4211161e4d0cc13ebfb83ca6c7ebc6f ? 239300 of 5960212

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