Bridge Analysis
What Bridge Analysis does
Bridges move value between chains. Bridge Analysis takes one transaction hash and tells you, in plain language, whether that transaction was a bridge deposit or a bridge withdrawal, which bridge contract it touched, and what asset moved.
It reads the chain. It never asks for your keys and it never moves funds.
When to use it
Use it when you have a transaction hash and a question like:
- Did this transaction actually send funds into a bridge, or is it something else?
- Which bridge was used, and how much moved?
- Someone told me funds were bridged to another chain. What can be confirmed from this transaction?
Where to find it
In the dApp sidebar, under INTELLIGENCE, open Bridge Analysis.
- Choose the network the deposit or withdrawal was sent on from the Network dropdown.
- Paste the transaction hash into the Transaction hash field, which expects 0x followed by 64 characters.
- Press Analyze to see what Cognivo can confirm about the bridge lifecycle.
What you get back
Cognivo reports on one leg of the bridge, the leg that happened on the network you selected. There are three outcomes.
Bridge activity detected. You get an Overview with the status, the source chain, the block, the time in UTC, the sender, the bridge contract and the asset moved. A Bridge contract section names the contract and links it to an explorer. Asset and amount shows the movement into or out of the bridge. Destination reference shows a destination chain, domain, recipient or reference ID when the transaction carries one. Lifecycle status records that the leg was observed on the chain you picked.
No bridge activity detected. The transaction was found and read, but nothing in it matched a grounded bridge deposit or withdrawal. Cognivo tells you which network it ran on and how many token transfers it moved, and stops there rather than labeling it a bridge.
Transaction not found. Cognivo could not find that hash on the network you chose. That is not a statement that the transaction does not exist. Check the hash and check that you picked the right network.
Some fields can come back missing. If the amount cannot be decoded, Cognivo says "amount not decoded" instead of guessing a number. If the transaction carries no readable destination chain or recipient, Cognivo says so and shows nothing in its place. A blank field means Cognivo could not read it, not that it is empty.
The limitation that matters
Cross-chain finalization is never assumed. Seeing a deposit on one chain does not prove the funds arrived on the other chain. Cognivo confirms arrival only by reading the destination chain separately, and this view shows one leg. When a transaction does carry a destination reference, Cognivo shows it and still says that arrival is only proven by reading that destination chain.
So a detected deposit means "this transaction sent value into this bridge contract". It does not mean "the money landed".
Chains and cost
Bridge Analysis covers Ethereum, Base and BNB Chain. Pick the network the transaction was sent on, because Cognivo looks only where you point it.
The tool is read only and free. There is no confirmation prompt and no credit charge for running it.
What to do next
To follow the funds hop by hop on the chain you are already looking at, use the Wallet Tracer. To read everything else that happened inside the same transaction, open Transaction Intelligence. For how credits work on the tools that do charge, see Billing and credits.