# π Overview
Welcome to the documentation of [**txdecoder.xyz**](https://txdecoder.xyz/) β on-chain transaction decoding infrastructure that transforms raw blockchain transaction data into meaningful user action\
\
Instead of parsing low-level transaction traces, logs, and calldata manually, our API decodes blocks, transactions into high-level events that are easy to understand and integrate. This allows you to focus on building products, dashboards, and analytics without worrying about protocol-specific decoding logic.\
* **What it does**\
Our API ingests blockchain transactions and decodes them into **user actions** such as:
* Token swaps, add/remove liquidity, liquidity pool initialization
* Token transfers
* Lending, borrowing, liquidation, flashloan actions
* Staking and farming interactions
* Stable coins mint/burn actions
* Bridge actions: enter to the chain or exit from the chain
* **Why it matters**
* Save development time: no need to maintain custom decoders for each protocol.
* Consistent schema: every action is normalized into a human-readable format.
* Faster insights: transform raw block data into analytics-ready information.
* **Who it is for**
* Data analysts building dashboards and reports
* Developers integrating blockchain activity into apps or wallets
* Trading platforms, DeFi monitors, and research teams
***
With [**txdecoder.xyz**](https://txdecoder.xyz/), you only need to provide a block\_number or tx\_hash β we handle the rest and return clean, standardized data of user actions. \
\
If you use WebSocket, you donβt need to do anything at all β we automatically push standardized data to you whenever a new block is available β real-time, zero effort.\
Just grab a cup of coffee and enjoy.
---
# Agent Instructions: 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:
```
GET https://txdecoder.gitbook.io/docs/introduction/overview.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.