Bitcoin Wallet & Transaction Tracer - Fund Flow Graph avatar

Bitcoin Wallet & Transaction Tracer - Fund Flow Graph

Pricing

from $17.00 / 1,000 address or transaction traceds

Go to Apify Store
Bitcoin Wallet & Transaction Tracer - Fund Flow Graph

Bitcoin Wallet & Transaction Tracer - Fund Flow Graph

Give Bitcoin addresses or transaction ids. Reads the public blockchain (keyless) and returns a follow-the-money brief: balance, total received/sent, ranked senders & recipients, a multi-hop fund-flow graph, and behavioural patterns. Read-only, agent-callable.

Pricing

from $17.00 / 1,000 address or transaction traceds

Rating

0.0

(0)

Developer

Centor Prat

Centor Prat

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a month ago

Last modified

Categories

Features

Limited permissions

Share

Bitcoin Wallet & Transaction Tracer — Fund Flow Graph

Follow the money on the public Bitcoin blockchain. Give one or more Bitcoin addresses (or transaction ids) and get back a structured "where did the funds come from / where did they go" brief: balance and lifetime totals, the ranked senders and recipients, a multi-hop fund-flow graph, and behavioural patterns (consolidation, peeling, high-velocity, dormant). Keyless, read-only, public ledger only — agent-callable.

For compliance / AML analysts, on-chain researchers, journalists, and AI agents doing blockchain investigation at scale.

What it does

  • Reads the public Bitcoin ledger via keyless explorer APIs (Blockstream Esplora, with mempool.space fallback) — no API key, no login.
  • Builds a per-address wallet summary and nets out who funded it and where it sent funds.
  • Expands the top counterparties into a multi-hop flow graph (nodes + directed, valued edges) so you can see the path of funds, not just one transaction.
  • Flags behavioural patterns an analyst looks for.
Output fieldMeaning
balanceBtc / balanceSatscurrent balance
totalReceivedBtc / totalSentBtclifetime in / out
txCount / txsAnalyzedtotal txs vs the most-recent window analysed
topSenders[] / topRecipients[]counterparties ranked by value (address + BTC)
flowGraphnodes[] + edges[] (from, to, direction, valueBtc, hop)
patterns[]consolidation / peeling-chain / high-velocity / dormant signals
signalactive / idle / emptied / unused / not-found
(tx mode) inputs[] / outputs[] / feeBtcfull transaction breakdown

Why not just ask an AI agent?

An agent can look up one address balance. It can't cheaply fetch dozens of transactions, net the counterparties by value across them, walk the top counterparties out several hops into a consistent graph, and detect peeling/consolidation patterns — deterministically, every time. That bounded graph traversal and aggregation at scale is exactly what this actor does for you.

Input

FieldTypeRequiredDescription
addressesarray of stringsone of theseBitcoin addresses (bc1… / 1… / 3…).
transactionIdsarray of stringsone of theseTransaction ids (64 hex) to break down.
hopsinteger (1–3)Fund-flow graph depth. 1 = direct counterparties.
maxCounterpartiesinteger (1–10)Top senders/recipients kept per address.
webhookUrlstringPOST the finished traces here as JSON.

Example input

{
"addresses": ["1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"],
"hops": 1,
"maxCounterparties": 5
}

Output

One record per address / transaction. Example output (trimmed, real run):

{
"id": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa",
"type": "address",
"signal": "active",
"balanceBtc": 57.66512665,
"totalReceivedBtc": 57.66512665,
"totalSentBtc": 0.0,
"txCount": 66959,
"txsAnalyzed": 27,
"uniqueSenders": 18,
"topSenders": [
{"address": "bc1pge0tgdp5c9wmjlq3ge694fne4jterr773u9amv0m4jum2cxa255s3r7k2j", "valueBtc": 0.00189895}
],
"flowGraph": {
"nodeCount": 4, "edgeCount": 3, "hops": 1,
"edges": [
{"from": "bc1pge0tgdp...255s3r7k2j", "to": "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa", "direction": "in", "valueBtc": 0.00189895, "hop": 1}
]
},
"patterns": [],
"disclaimer": "Public blockchain data only. Traced flows and patterns are signals to review, not proof of ownership, identity, or wrongdoing."
}

Use cases

  • AML / compliance triage — see an address's counterparties and flow before onboarding or paying it.
  • Incident response — trace where stolen/scammed funds moved across hops.
  • Journalism & research — document the public money trail of a wallet or transaction.
  • AI investigation agents — one call returns a structured flow graph to reason over.

Ready-made tasks

For AI agents / MCP

Every public Apify actor is callable through the Apify MCP server.

https://mcp.apify.com/?tools=actors,docs,centorprat/bitcoin-wallet-transaction-tracer

Loads as the tool centorprat--bitcoin-wallet-transaction-tracer. Claude Code:

claude mcp add apify -- npx -y @apify/actors-mcp-server --actors centorprat/bitcoin-wallet-transaction-tracer

Alerts / scheduling

Set webhookUrl and schedule the actor to re-trace a watched address — the fresh brief is POSTed to Make/Zapier/your endpoint, so you're notified when a wallet moves funds.

FAQ

Which chains? Bitcoin (mainnet). Addresses in bech32 (bc1…) and base58 (1…, 3…), plus transaction ids.

Does it need an API key? No — it reads public explorer APIs anonymously.

How many transactions does it analyse? The most recent ~25–50 per address (a brief, not a full re-index); txsAnalyzed and a note tell you when an address has more history than the window.

How deep can it trace? Up to 3 hops, bounded for speed (a safety cap on nodes per trace).

Does it identify who owns an address? No. It reports only public on-chain flows and patterns as signals to review — never an identity or an accusation of wrongdoing.

Is this legal? It reads the public Bitcoin ledger, which is open by design. No private data, no keys, no deanonymisation.

Values in BTC or satoshis? Both — *Btc fields and *Sats fields.

How fast? A couple of seconds for 1 hop; a few seconds for deeper graphs.

Cost? Pay-per-event, one charge per address/transaction successfully traced. Invalid/not-found inputs aren't billed.

Data & attribution

All data is the public Bitcoin blockchain, read via the keyless Blockstream Esplora API (mempool.space fallback). No keys, no personal data. Results are computed signals, not financial, legal, or compliance advice.