Hi everyone.
One recurring UX challenge I’ve noticed on Stacks is that transactions are often difficult to understand for non technical users. Explorers expose raw JSON and low level fields, but they don’t always explain what actually happened in a transaction or why it matters.
To explore this problem, I built an open source tool called Explain My Transaction.
The idea is simple:
you paste a Stacks transaction hash, and the app fetches the real on-chain data, parses it deterministically, and generates a plain english explanation of what happened. It currently handles successful, failed, and pending transactions, and shows a small summary (sender, transaction type, fee, block height) alongside the explanation.
The project is currently at a working MVP stage:
• Live demo available
• Public GitHub repository
• Focused on correctness, clarity, and clean architecture rather than analytics or AI heavy features
I’m sharing this here because I’d really value community feedback before taking the next steps. In particular, I’d love input on:
• Which Stacks transaction types are most confusing today?
• Where do users or new builders struggle the most when trying to understand on-chain activity?
• Would a future “wallet story” view (a narrative summary of a wallet’s activity over time) be useful for onboarding or education?
Links for context:
GitHub: GitHub - Grimaldo0147/explain-my-transaction: Explain Stacks transactions in plain English
Live demo: https://explain-my-transaction.vercel.app/
Thanks in advance, I’m looking forward to learning from the community and improving this in ways that are genuinely useful for the Stacks ecosystem.