Journal article
Spectroscopic evidence of superconductivity pairing at 83 K in single-layer FeSe/SrTiO3 films
- Abstract:
- AbstractSingle-layer FeSe films grown on the SrTiO3 substrate (FeSe/STO) have attracted much attention because of their possible record-high superconducting critical temperature (Tc) and distinct electronic structures. However, it has been under debate on how high its Tc can really reach due to the inconsistency of the results from different measurements. Here we report spectroscopic evidence of superconductivity pairing at 83 K in single-layer FeSe/STO films. By preparing high-quality single-layer FeSe/STO films, we observe strong superconductivity-induced Bogoliubov back-bending bands that extend to rather high binding energy ~ 100 meV by high-resolution angle-resolved photoemission measurements. They provide a new definitive benchmark of superconductivity pairing that is directly observed up to 83 K. Moreover, we find that the pairing state can be further divided into two temperature regions. These results indicate that either Tc as high as 83 K is achievable, or there is a pseudogap formation from superconductivity fluctuation in single-layer FeSe/STO films.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 4.6MB, Terms of use)
-
- Publisher copy:
- 10.1038/s41467-021-23106-y
Authors
- Publisher:
- Nature Research
- Journal:
- Nature Communications More from this journal
- Volume:
- 12
- Issue:
- 1
- Pages:
- 2840-2840
- Article number:
- 2840
- Publication date:
- 2021-05-14
- DOI:
- EISSN:
-
2041-1723
- ISSN:
-
2041-1723
- Language:
-
English
- Keywords:
- Pubs id:
-
1980107
- Local pid:
-
pubs:1980107
- Source identifiers:
-
W3095862798
- Deposit date:
-
2026-06-10
- ARK identifier:
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.
Terms of use
- Copyright date:
- 2021
- Licence:
- CC Attribution (CC BY)
If you are the owner of this record, you can report an update to it here: Report update to this record