> 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/waiting-transactions.md).
# Waiting Transactions
**Overview**
This indicator measures the in-flight or in-process transactions within a DeFi bridge protocol. This metric quantifies the number of transactions that have successfully left the originating blockchain but have not yet been confirmed or finalized on the destination blockchain. It's a crucial indicator of the operational status and efficiency of cross-chain transactions facilitated by the bridge.
**How can I use it?**
A low number of transactions pending completion suggests high operational efficiency of the bridge, indicating swift processing and minimal delays in cross-chain transfers. Conversely, a high number could signal bottlenecks or inefficiencies.
Monitoring this metric can provide insights into the health and performance of both the bridge protocol and the connected blockchains. A sudden increase in pending transactions may indicate congestion, technical issues, or scalability limits being reached.
Pending transactions represent a state of uncertainty; the longer a transaction is in this state, the higher the risk of failure or market changes impacting the transaction outcome. This indicator helps users assess the risk associated with using the bridge at any given time.
---
# 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/waiting-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.
