An explanation can be simple, and holding the entire chain of simple ideas in your head to 'understand' some bigger idea can be difficult.
At some point, you have a body of knowledge, your 'understanding' that satisfies your curiosity (or you get exhausted and move on).
As an example of this, you can have complex code made of entirely simple and easy to understand functions. But the complexity appears in the combination. That complexity can be far higher than were you to have more complex functions in the program. Which this is a common mistake people make that lead to tech debt. A lot of people try to simplify code by making it "understandable" without setting a floor to who needs to understand it and with how much time. If you don't, that floor gets lower each year.
If you can't think of an example of the first case, most machine learning models suffice. Take a simple feed forward ReLU model. It's trivial to understand ReLU. It's nearly trivial to understand the individual neuron. Yet I, as someone who wrote their PhD thesis on neural architectures, would call bullshit on anyone claiming they "really" understand what's going on in a deep network.