Aptos Mainnet Transactions Scraper

Aptos Mainnet Transactions Scraper

Scrape Aptos mainnet transactions by ledger version, up to a million per run. Each transaction returns its hash, sender, payload, gas used, and timestamp. No node or API key required. Export to CSV, JSON, Excel, or XML.

Running an Aptos full node or parsing the REST API yourself means syncing terabytes of state and writing custom deserializers. This Actor reads the public transaction stream directly, starting from any ledger version you choose, and returns each transaction in one flat, predictable schema. It handles pagination and rate limits so you get clean data without infrastructure work.

Who uses it	What they scrape Aptos Mainnet for
Blockchain analysts	Audit on-chain activity for a specific protocol or wallet address over a date range.
DApp developers	Debug user interactions by pulling the raw transaction payloads your frontend submitted.
Tax and compliance teams	Reconstruct a wallet's complete transaction history for reporting.
Data engineers	Feed a data warehouse with raw Aptos transactions for internal dashboards.

What it does

This Actor collects Aptos mainnet transactions from a specified start version and returns each one as a flat row with its hash, sender, payload, gas, and timestamp.

• 🔢 Version range: start from any ledger version and pull forward up to your item limit.
• ⚡ Latest block: leave the start version empty and the Actor begins at the current chain tip.
• 📦 Flat output: every transaction is a single row, ready for CSV, JSON, Excel, or XML export.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with Aptos Mainnet data

📈 Reconstruct wallet history.

A compliance officer enters a start version near account creation and pulls every transaction touching a known address to build a full activity log.

🔍 Debug dApp interactions.

A developer sets the start version to a block before a user's failed transaction and inspects the raw payload to find the root cause.

📊 Feed an analytics pipeline.

A data engineer schedules daily runs from the last imported version and loads new transactions into a ClickHouse database for dashboard queries.

Why choose this scraper

	What you get
No node required	Reads the public Aptos mainnet feed so you skip syncing and storage.
Fixed schema	Every transaction arrives with the same fields, regardless of payload type.
Scalable runs	Pull up to a million transactions in one go for bulk analysis.

How it compares

No other Store actor targets Aptos Mainnet the same way, so the honest comparison is with the alternatives teams actually weigh.

	Aptos Mainnet Transactions Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When Aptos Mainnet 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 from a start ledger version and a maximum item count, and the run stops when either the limit is reached or the chain tip is hit. The Input tab lists every parameter.

A first run with the defaults:

{
  "maxItems": 10
}

A larger pull:

{
  "maxItems": 200
}

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

1. Create a free Apify account with $5 in credit.
2. Open the Aptos Mainnet Transactions Scraper.
3. Set your inputs and any filters, then click Start.
4. 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 Aptos Mainnet through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/aptos-mainnet-transactions-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check that your start version is not ahead of the current chain tip. If you entered a future version, leave the field empty to start from the latest block.

Why is the run slow?

The Aptos public endpoint throttles requests. The Actor respects these limits. For sustained high throughput, consider running your own node and using a custom endpoint.

Why are some payload fields empty?

Not every transaction includes a payload (e.g., certain system transactions). Empty fields reflect what the chain returned for that version.

Why did my run stop before reaching max items?

The Actor stops when it reaches the current chain tip. If you requested more items than exist after your start version, the run ends early.

Why do I see a 'version not found' error?

The start version you entered may have been pruned from the public endpoint. Try a more recent version or leave the field empty.

FAQ

Question	Answer
Do I need an Aptos node or API key to use this?	No. The Actor reads from public Aptos mainnet endpoints. You do not need to run a node, register an app, or manage API keys.
What does a transaction row include?	Each row contains the transaction hash, sender address, sequence number, payload, gas used, gas unit price, expiration timestamp, and the ledger version it was committed in.
How do I start from the latest block?	Leave the start version field empty. The Actor will begin at the current chain tip and work backwards as new blocks are produced.
Can I scrape more than a million transactions?	The maximum per run is 1,000,000 items. For larger volumes, run the Actor multiple times, setting the start version to the last version you received plus one.
What happens if I hit the rate limit?	The Actor backs off and retries automatically. If the limit persists, the run pauses and resumes when the endpoint accepts requests again.
Does this include Move contract events?	The Actor returns the raw transaction. Events emitted during execution are part of the transaction payload and are included in the payload field.
Can I filter by sender address?	The Actor pulls all transactions in the version range. Filter by sender after export using your own scripts or spreadsheet tools.
Is this mainnet only?	Yes. This Actor targets Aptos mainnet. Testnet and devnet are not supported in this version.
What export formats are supported?	You can export your dataset to CSV, JSON, Excel, or XML from the Apify platform.
How do I resume an interrupted run?	Check the last successfully scraped version in your dataset, then start a new run with that version as the start version.

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