Add transaction investigation example to setup guide - #2748
Conversation
Added an example for investigating Stellar transactions using a public blockchain explorer and the Horizon API.
EHESPO
left a comment
EHESPO
left a comment
There was a problem hiding this comment.
https://stellar.expert/explorer/public/tx/f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b6c00d769c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ```bash | ||
| curl "https://horizon.stellar.org/transactions/f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce" |
There was a problem hiding this comment.
Starting this bash fence without a closing ``` makes Markdown treat the rest of the file as part of the code block; in this commit that swallows the duplicated heading and transaction explanation instead of rendering them as documentation. Add the closing fence after the curl command and remove the duplicate block so the new section renders correctly.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Pull request overview
Adds a transaction investigation example to the smart-contract setup guide.
Changes:
- Adds explorer and Horizon lookup examples.
- Introduces duplicated content, an unclosed code fence, and outdated Horizon guidance.
Recommendation: NEEDS-CHANGES — fix the malformed MDX and align with current RPC guidance.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| [View transaction on StellarExpert](https://stellar.expert/explorer/public/tx/f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce) | ||
|
|
||
| The transaction should be treated as a diagnostic example only. Applications must retrieve the transaction and operation results from Horizon when determining the protocol-level result of a transaction. |
[View this transaction on StellarExpert](https://stellar.expert/explorer/public/tx/f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce) Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Added an example for investigating Stellar transactions using a public blockchain explorer and the Horizon API.