can message queues simplify distributed transaction management, or do they just make things more complicated?

ive been thinking about how to manage distributed transactions in microservice architectures. the usual two-phase commit (2PC) approach can be complex and introduce tight coupling. im wondering if using message queues, perhaps with a saga pattern, could offer a more manageable alternative. has anyone here successfully implemented something like this? what were the challenges and benefits compared to traditional methods?