uPlexa Block Explorer

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

Tx hash: 8cde7dc597d559fe3eb259e7a320f32672c4f77cb93989e6c8220e1f642766b8

Tx prefix hash: eeb9c185a78df09d76cc2ae17f9982f678e01091aeb807cab8a6454b10e61fe6
Tx public key: a080cb74ba6ef6e60ad00a013e9384f588efea57e3b32f5ea2617b00bcee1393
Timestamp: 1590192155 Timestamp [UCT]: 2020-05-23 00:02:35 Age [y:d:h:m:s]: 00:003:16:39:42
Block: 442265 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 2674 RingCT/type: yes/0
Extra: 01a080cb74ba6ef6e60ad00a013e9384f588efea57e3b32f5ea2617b00bcee13930211000000352fe19e00000000000000000000

1 output(s) for total of 1978.50 upx

stealth address amount amount idx
00: cb0c03fed47dd9da52a0d075aec48fa7f4659e419805b7c81794483b2868b139 1978.50 2405319 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



{ "version": 2, "unlock_time": 442325, "vin": [ { "gen": { "height": 442265 } } ], "vout": [ { "amount": 197850, "target": { "key": "cb0c03fed47dd9da52a0d075aec48fa7f4659e419805b7c81794483b2868b139" } } ], "extra": [ 1, 160, 128, 203, 116, 186, 110, 246, 230, 10, 208, 10, 1, 62, 147, 132, 245, 136, 239, 234, 87, 227, 179, 47, 94, 162, 97, 123, 0, 188, 238, 19, 147, 2, 17, 0, 0, 0, 53, 47, 225, 158, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2019-01-05-0432f03 (1.1) | uPlexa version: 0.2.0.2-release