Skip to content

Add transaction investigation example to setup guide #2748

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
EHESPO wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add transaction investigation example to setup guide #2748

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b6c00d7
Add transaction investigation example to setup guide
EHESPO Aug 14, 2026
4427ecd
Potential fix for pull request finding
EHESPO Aug 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/build/smart-contracts/getting-started/setup.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -289,3 +289,20 @@ echo "source (stellar completion --shell elvish)" >> ~/.elvish/rc.elv

[rust]: https://www.rust-lang.org/
[stellar cli]: #install-the-stellar-cli
## Transaction Investigation Example

Developers and agents can inspect a Stellar transaction using a public blockchain explorer or the Horizon API.

Example transaction:

`f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce`

[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.

For example:

```bash
curl "https://horizon.stellar.org/transactions/f9d806e098ddb4596e56e2e60a776dbae0c6ca2329f5a276b9abf8edf3fa99ce"
Comment on lines +306 to +307

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Close the transaction curl code fence

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 👍 / 👎.

```