验证数据展示
经过测试的应用
| Positive IF/ICC detected in | PC-12 cells |
推荐稀释比
| 应用 | 推荐稀释比 |
|---|---|
| Immunofluorescence (IF)/ICC | IF/ICC : 1:50-1:500 |
| It is recommended that this reagent should be titrated in each testing system to obtain optimal results. | |
| Sample-dependent, Check data in validation data gallery. | |
产品信息
CL488-25537 targets YTHDF3-specific in IF/ICC applications and shows reactivity with human, mouse samples.
| 经测试应用 | IF/ICC Application Description |
| 经测试反应性 | human, mouse |
| 免疫原 |
CatNo: Ag22374 Product name: Recombinant human YTHDF3 protein Source: e coli.-derived, PET28a Tag: 6*His Domain: 284-351 aa of BC052970 Sequence: SVVKAPPTQPVLPPQTIIQQPQPLIQPPPLVQSQLPQQQPQPPQPQQQQGPQPQAQPHQVQPQQQQLQ 种属同源性预测 |
| 宿主/亚型 | Rabbit / IgG |
| 抗体类别 | Polyclonal |
| 产品类型 | Antibody |
| 全称 | YTH domain family, member 3 |
| 别名 | FLJ31657, YTH domain family protein 3, YTH domain family, member 3, YTHDF3 |
| 计算分子量 | 585 aa, 64 kDa |
| 观测分子量 | 64 kDa |
| GenBank蛋白编号 | BC052970 |
| 基因名称 | YTHDF3 |
| Gene ID (NCBI) | 253943 |
| RRID | AB_3672794 |
| 偶联类型 | CoraLite® Plus 488 Fluorescent Dye |
| 最大激发/发射波长 | 493 nm / 522 nm |
| 形式 | Liquid |
| 纯化方式 | Antigen affinity purification |
| UNIPROT ID | Q7Z739 |
| 储存缓冲液 | PBS with 50% glycerol, 0.05% Proclin300, 0.5% BSA, pH 7.3. |
| 储存条件 | Store at -20°C. Avoid exposure to light. Stable for one year after shipment. Aliquoting is unnecessary for -20oC storage. |
背景介绍
YTHDF3, also named as YTH domain-containing family protein 3, is a 585 amino acid protein, which contains 1 YTH domain. YTHDF3 specifically recognizes and binds N6-methyladenosine (m6A)-containing RNAs. M6A is a modification present at internal sites of mRNAs and some non-coding RNAs and plays a role in the efficiency of mRNA splicing, processing and stability. Our antibody 25537-1-AP specially reacts with YTHDF3 protein.
实验方案
| Product Specific Protocols | |
|---|---|
| IF protocol for CL Plus 488 YTHDF3-specific antibody CL488-25537 | Download protocol |
| Standard Protocols | |
|---|---|
| Click here to view our Standard Protocols |
