> For the complete documentation index, see [llms.txt](https://resources.defirisk.intotheblock.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.defirisk.intotheblock.com/axelar-interchain-tokens/orphan-transactions.md). # Orphan Transactions **Overview** This indicator shows the count of transactions that were initially verified and accepted by the network but were later not processed, often due to discrepancies in network synchronization or other network issues. Orphan transactions represent a subset of transactions that, for a period, were considered valid by part of the network but ultimately were not processed. **How can I use it?** A high number of orphan transactions may signal network unreliability or significant latency issues. This can help identify underlying problems that need to be addressed to ensure reliable transaction processing. Comparing the orphan transaction rate across different periods can provide insights into the bridge stability and efficiency. A lower rate or no existing orphan transactions is generally indicative of a more robust and reliable network. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://resources.defirisk.intotheblock.com/axelar-interchain-tokens/orphan-transactions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.