Safe Global Multisig Transactions Scraper
Pricing
from $7.50 / 1,000 results
Safe Global Multisig Transactions Scraper
Collects all transactions for a Safe multisig wallet address on a chosen EVM network and returns each one as a flat row with status, value, confirmations, and execution details.
Pricing
from $7.50 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
8 days ago
Last modified
Categories
Share
Safe Global Multisig Transactions Scraper
Scrape multisig wallet transactions from any Safe address across 8 EVM networks. Every transaction includes its status, value, data, confirmations, and execution details. No RPC endpoint or archive node required. Export to CSV, JSON, Excel, or XML.
Safe is the most widely used multisig wallet on Ethereum and EVM chains, but pulling a clean transaction history for audits, accounting, or monitoring means either clicking through pages of the web app or writing custom subgraph queries. This actor reads the Safe Transaction Service API directly for any Safe address you provide, across Ethereum mainnet, Arbitrum, Base, Optimism, Polygon, Gnosis Chain, BNB Chain, and Avalanche. You get every transaction in one flat dataset, ready for analysis.
| Who uses it | What they scrape Safe Global for |
|---|---|
| Crypto accountants | Reconciling multisig treasury movements for monthly close or tax reporting |
| DAO operators | Auditing proposal execution and signer participation across governance cycles |
| Security analysts | Monitoring outgoing transactions from a known Safe for anomaly detection |
| Onchain researchers | Studying multisig usage patterns and signer behavior over time |
What it does
This Actor collects all transactions for a given Safe multisig wallet address on a chosen EVM network and returns each one as a flat row with its status, value, confirmations, and execution details.
- 🔗 Multi-network support: Ethereum mainnet, Arbitrum, Base, Optimism, Polygon, Gnosis Chain, BNB Chain, and Avalanche.
- 📊 Full transaction detail: status, value, data, operation type, confirmations, executor, and timestamps.
- 📦 Bulk collection: pull up to one million transactions per run for long-lived Safes.
- 🔁 Deterministic ordering: transactions are returned in the order the Safe executed them, oldest first.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with Safe Global data
🧾 Reconcile a DAO treasury.
A DAO accountant runs the actor monthly on the DAO's Safe address on mainnet, exports to CSV, and matches every outgoing transaction against offchain payment requests.
🔍 Audit signer participation.
A security firm pulls a year of transactions for a client's Safe on Arbitrum and checks which signers confirmed each transaction, flagging any that executed with fewer than the required threshold.
📈 Track multisig activity trends.
An onchain analyst collects all transactions from a set of known protocol Safes across multiple networks and plots weekly execution volume to gauge development activity.
🚨 Monitor for unexpected outflows.
A risk operator sets the actor to run daily on a treasury Safe on Optimism and pipes the output into a detection rule that alerts if any transaction exceeds a value threshold.
Why choose this scraper
| What you get | |
|---|---|
| No RPC or archive node | The actor queries the Safe Transaction Service API, so you do not need your own node or indexer. |
| Eight chains, one actor | Switch networks with a dropdown. No separate scraper for each chain. |
| Clean flat output | Every transaction is one row with the same schema, regardless of type or network. |
| Audit-ready data | Includes confirmations per signer, execution date, and transaction hash for verifiability. |
How it compares
No other Store actor targets Safe Global the same way, so the honest comparison is with the alternatives teams actually weigh.
| Safe Global Multisig Transactions Scraper | Build it in-house | By hand | |
|---|---|---|---|
| Setup | Run it now, zero config | Days of engineering | None, but hours per pull |
| When Safe Global changes | Maintained for you | You fix it | You re-learn the page |
| Proxies, retries, anti-bot | Built in | Your problem | Browser only |
| Output | Fixed JSON schema, CSV/Excel export | Whatever you build | Copy-paste |
| Cost | Pay per result | Engineering time | Analyst hours |
Configure the run
Drive the Actor with a Safe address and a network choice, then set a maximum transaction count to cap the run. The Input tab lists every parameter.
A first run with the defaults:
A larger pull:
Pricing
Pay-per-result: $0.0085 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.85 |
| 1,000 results | $8.50 |
| 10,000 results | $85.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the Safe Global Multisig Transactions Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to Safe Global through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting no results?
Check that the Safe address is correct and in checksum or lowercase format. Also verify that the Safe has transactions on the network you selected. A newly created Safe with no activity will return an empty dataset.
Why does the actor return fewer transactions than I expected?
The actor stops when it reaches the maxItems limit you set or when there are no more transactions. Increase maxItems if you need more, up to 1,000,000.
Why are some transactions missing confirmations?
Pending transactions that have not yet gathered enough confirmations will show fewer signers. Re-run the actor after the transaction executes to get the full confirmation set.
Why did the run fail with a network error?
The Safe Transaction Service API may be temporarily unavailable for the selected network. Wait a minute and retry. If the error persists, try a different network to isolate whether the issue is network-specific.
Can I get the decoded function calls instead of raw hex data?
The actor returns the raw data field as provided by the Safe API. To decode function calls, you will need the contract ABI and a decoding step in your pipeline.
FAQ
| Question | Answer |
|---|---|
| What is a Safe address? | A Safe address is the onchain contract address of a Safe multisig wallet. It starts with 0x and is 42 characters long. You can find it in the Safe web app under the wallet name or in the URL when you open your Safe. |
| Which networks does this actor support? | It supports Ethereum mainnet, Arbitrum, Base, Optimism, Polygon, Gnosis Chain, BNB Chain, and Avalanche. Select the network from the dropdown when you configure the run. |
| Does this actor require an API key? | No. The actor queries the public Safe Transaction Service API endpoints. No API key, RPC URL, or wallet connection is needed. |
| What transaction fields are included in the output? | Each row includes the transaction hash, status, value, data, operation type, nonce, confirmations with signer addresses, executor address, submission date, and execution date. |
| Can I scrape transactions from multiple Safes in one run? | One run handles one Safe address. To scrape multiple Safes, run the actor once per address, or use an Apify task with an array of addresses. |
| How are transactions ordered in the output? | Transactions are returned in execution order, oldest first, matching the nonce sequence of the Safe. |
| Does this actor handle ERC-20 token transfers? | The actor returns the raw transaction data field. Token transfers that happen as part of a transaction are encoded in that data field. You can decode them downstream using an ABI. |
| What is the maximum number of transactions I can collect? | You can set the maximum up to 1,000,000 transactions per run. The actor stops when it reaches that count or when there are no more transactions for the Safe. |
| Does this actor work with Safe wallets on L2 networks? | Yes. It supports Arbitrum, Base, Optimism, Polygon, Gnosis Chain, BNB Chain, and Avalanche in addition to Ethereum mainnet. |
| Can I filter by transaction status? | The actor collects all transactions regardless of status. You can filter the output dataset by the status field after the run completes. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Safe Ecosystem Foundation. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
