I'm also autistic, and had similar issues early in my career which turned out to be "too much information".
When explaining code, you need to paint with broad strokes. There are all sorts of nuances that would normally require extensive and careful explanations, but what you really want to do is a kind of ELI5 approach, then go into more detail if people ask for it (they almost never do).
It also helps to just keep practicing, getting feedback afterwards (people don't usually want to give feedback, but I've had success prefacing it with "I'm trying to improve my explanations, so solid feedback on anything that was confusing will really help!").
When explaining code, you need to paint with broad strokes. There are all sorts of nuances that would normally require extensive and careful explanations, but what you really want to do is a kind of ELI5 approach, then go into more detail if people ask for it (they almost never do).
It also helps to just keep practicing, getting feedback afterwards (people don't usually want to give feedback, but I've had success prefacing it with "I'm trying to improve my explanations, so solid feedback on anything that was confusing will really help!").