> For the complete documentation index, see [llms.txt](https://docs.raybot.app/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raybot.app/start/getting-started/use-cases/what-is-this-transaction.md).

# What Is This Transaction?

If you've ever dug into a wallet's transaction history, you've definitely seen it.

A wallet receives or sends funds — and the counterparty is just a raw address. No label, no tag, no context. Just a string of characters staring back at you.

> *What is this? A DEX? A bridge? A CEX deposit? Another wallet? Some random DApp?*

Today we break it down — and learn how to identify almost any transaction quickly.

When you fully understand how a trader interacts with different addresses, you start seeing the complete picture — not just fragments. You can trace the full flow of funds, find alpha in a wallet's behavior, and uncover sub-wallets that no one else is looking at.

The best part? You're digging this up yourself — before it shows up in anyone's posts, before the influencers talk about it, before the crowd even knows it exists.

**Information is power. And you got it first.**

***

### ⛓️ Solana vs EVM: Addresses and Contracts

Before we start identifying transactions, we need to understand one fundamental difference between these two blockchains.

**In Ethereum (EVM) everything is straightforward:**

* 🔑 A wallet is a wallet
* 📄 A smart contract is a smart contract

Two types. Easy to distinguish. Done.

**In Solana — it's a different story.**

Every address is simply an **account**. And that account can be anything: a wallet, a program (smart contract), or a data storage. The address that just sent you 1 SOL might look like a regular wallet — but it could actually be a protocol's hot wallet controlled by a program.

Think of it like a regular bank where you can't tell the difference between a personal account and an ATM — they look identical from the outside.

> 📌 That's exactly why we need services that can identify these transactions for us.

***

### 🛠️ Tools to Identify Any Address

Here are the top 3 free tools that will cover **95% of all unknown addresses** across both networks:

**🔍** [**intel.arkm.com**](https://intel.arkm.com) Probably one of the best blockchain analytics platforms out there. Most protocols, DApp addresses, CEX wallets — everything has a name here. And it's fully multichain.

**🔍** [**orbmarkets.io**](https://orbmarkets.io) A solid solution specifically for Solana. Clean, fast, and surprisingly effective for identifying unknown addresses in the ecosystem.

**🔍** [**debank.com**](https://debank.com) The go-to for EVM networks. Most protocols and contracts are already labeled — paste an address and get instant context.

***

🧠 **Now you have the tools. The rest is practice.** Paste the address — get the answer. It's that simple.


---

# 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://docs.raybot.app/start/getting-started/use-cases/what-is-this-transaction.md?ask=<question>&goal=<endgoal>
```

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