Uplexa Block Explorer

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

Transaction

Autorefresh is OFF
Tx hash: 5b9086c60d23ddb81005e7a119740df8bc3c4cae9042f8d8fd9e2642e4374419 Tx public key: c15fe5c0c916bea574dc3174e72ea3439a8b856fc1348f32fcb44d5002b3ca74
Timestamp: 1685081993 Timestamp [UCT]: 2023-05-26 06:19:53 Age [y:d:h:m:s]: 00:131:02:38:17
Block: 1232854 Fee (per_kB): 0.00 (0.00) Tx size: 0.1318 kB
Tx version: 2 No of confirmations: 94313 RingCT/type: yes/0
Extra: 01c15fe5c0c916bea574dc3174e72ea3439a8b856fc1348f32fcb44d5002b3ca7402110000000584fe794e000000000000000000032100e78f0324ce12000e3ce40ef3e3f8be5c32cc2d81931f51030e4a0790423e0df1

1 output(s) for total of 1637.70 upx

stealth address amount amount idx
00: c0e90f228e143c7651fc4b688fe1dd9f567e3c199448f3a47d510314813d4fee 1637.70 5527263 of 0

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