uPlexa Block Explorer

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

Tx hash: af1f85b06ff4c8cbfcba12ce9da93e10f79fde4c7feca3492eb28cb768fbe5e6

Tx prefix hash: 2d9621a59532b89d4a9f7c51ff96824f2454db5e11fe6a886fdad41ca0a76bbb
Tx public key: d3bdf1da3f42579676dd185ecb60d9e0056cba625439f10c63c2cb616b4e700e
Timestamp: 1581670180 Timestamp [UCT]: 2020-02-14 08:49:40 Age [y:d:h:m:s]: 00:177:10:37:38
Block: 371248 Fee (per_kB): 0.00 (0.00) Tx size: 0.0977 kB
Tx version: 2 No of confirmations: 127869 RingCT/type: yes/0
Extra: 01d3bdf1da3f42579676dd185ecb60d9e0056cba625439f10c63c2cb616b4e700e021100000077cd9db40000000001000000d500

1 output(s) for total of 2010.86 upx

stealth address amount amount idx
00: 1f8938e334a65b7b808e85fa20847ceaa3bcf6a2e9886f16e9910bbb23385956 2010.86 2092544 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": 371308, "vin": [ { "gen": { "height": 371248 } } ], "vout": [ { "amount": 201086, "target": { "key": "1f8938e334a65b7b808e85fa20847ceaa3bcf6a2e9886f16e9910bbb23385956" } } ], "extra": [ 1, 211, 189, 241, 218, 63, 66, 87, 150, 118, 221, 24, 94, 203, 96, 217, 224, 5, 108, 186, 98, 84, 57, 241, 12, 99, 194, 203, 97, 107, 78, 112, 14, 2, 17, 0, 0, 0, 119, 205, 157, 180, 0, 0, 0, 0, 1, 0, 0, 0, 213, 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