flowtrace

🔎 What just changed in this account?

Did the balance move? Was a key added? Did the contract code change?

Give FlowTrace an account ID. Get net balance changes, access-key changes and code-hash differences in one report, with both finalized block anchors ready for review.

Real mainnet capture, November 3, 2026. Waiting time is compressed. Two snapshots show net differences, not a full transaction history.

Try it with wrap.near →

Related MCP server: ryntra-solana-evidence

🗣️ Ask a question. Let the agent check.

Drop this into chat:

Compare the balance and permission changes of wrap.near over the last 100 block heights.

The agent calls real tools and returns results, block heights and an expandable tool trace. Open the same result in the manual panel when you want a closer look.

Actual tool call captured on November 3, 2026. Values are historical; the web UI is currently in Chinese.

Open chat and ask your question →

🛑 Sending 0.01 with a 0.001 request limit?

Flag the mismatch before wallet review.

FlowTrace checks FT balances, recipient existence, token storage, fee reserves and a per-request amount limit. This public example actually returns a blocked preflight:

A read-only rules check. The amount limit applies to this preflight input; it is not an on-chain authorization or spending cap.

Checks can produce an unsigned template for wallet review. Funds and signing stay with your wallet.

Open the amount-limit example →

💸 “Does this receipt match what we agreed?”

Provide the expected amount, asset, recipient and target transaction. FlowTrace checks the transaction's net FT events, lists mismatches and missing evidence, and can also read 1Click channel status.

Useful for payment troubleshooting, merchant-reconciliation prototypes and agents that need payment evidence. Order association is declared by the caller; channel status and merchant receipt are checked separately.

Try the historical payment example →

🧩 Give your own agent the tools

The same checks work in the browser and in clients that support HTTP MCP:

{
  "mcpServers": {
    "flowtrace": {
      "url": "https://www.darkchunk.win/collect/mcp"
    }
  }
}

Inspect → compare → investigate → preflight. Structured results help your agent continue the task and help you download the evidence for review.

Local setup / stdio / REST → · Full parameters → · Companion Skill →

🚀 Take it for a spin

1. Open the live demo. No wallet connection needed.

2. Click 填入公开示例 (Fill public example), then 查询两个区块并核对 (Compare).

3. Review the changes and blocks. Download your first JSON report.

Want your own instance? Node.js 22+, then:

git clone https://github.com/yinbowen-dc/FlowTrace.git
cd FlowTrace
npm ci
npm start

Open http://127.0.0.1:8804/agent/. Manual forms, MCP and REST need no model key. AI chat uses server-side configuration; see the integration guide.

🛠️ Working today. More to build.

This is v0.4.1 MVP: web chat, manual checks, 8 MCP tools and 4 workflows are implemented. The v0.4.1 release passed 81 tests; mainnet, MCP-client and real model-tool checks were performed separately.

Up next: watchlists → scheduled collection → change notifications, plus transaction-history indexing and merchant order integration. These features are not live yet. Come help build them.

Plan → · v0.4.1 release → · Ideas and bugs → · Contribute → · Mainnet verification → · Offline payment evidence →

• Mainnet data is queried on demand. Continuous monitoring, alerts and arbitrage execution are not implemented.

• Account reports cover native NEAR plus USDC, USDT and wNEAR, not other tokens, NFTs, staking-pool shares or Intents internal balances.

• Comparisons show net snapshot differences. Zero net movement does not establish inactivity; a key change does not establish theft. Historical-data failures remain unknown.

• A payment check does not prove invoice ownership, full cross-chain settlement or source-chain refunds. Channel success alone is not merchant-receipt proof.

• Preflight is not simulation or an execution guarantee. FlowTrace does not hold keys, sign, broadcast, swap or refund. FunctionCall key allowance is a gas budget.

• Chat messages and needed tool results go to OpenAI; the service does not persist chat bodies. Imported orders remain in the browser's unencrypted localStorage. Never enter wallet secrets or API keys.

• Public endpoints have rate and concurrency limits and no production SLA. RPC data is an upstream observation, not an independent light-client proof. The web UI is currently in Chinese.

See the full data and integration guide (Chinese) and visual asset notes.

Built for NEAR HACKATHON 2026 with AI coding assistance. Submission is pending; see preparation. The existing domain is hosting infrastructure; the earlier market dashboard is not a source or runtime dependency.

Uses the official MCP SDK, OpenAI Agents SDK, Zod, NEAR RPC, NearBlocks sample discovery and optional 1Click status, each under its own license. MIT · FlowTrace contributors