WatchExplorechain 4663
← Deployed Zaps

0xfF4Dd8987338D6F045F9f6e45643cE5E70e14D68

Everything below was read from Robinhood Chain at one pinned block. This page reports what the contract stores and what its own logs say. Nothing is estimated, modelled, or priced. A read that fails is reported as unavailable, never as a zero.

View on Blockscout ↗

Verification

read at one pinned blockFork in Composer✓ Verified onchain

The factory's own ZapCreated log names this address. Its runtime is the EIP-1167 clone of the canonical implementation. The policy it exposes rehashes to the policyHash it committed to.

Read at block
23,280,727
Snapshot taken
7/30/2026, 11:30:35 AM
Lifecycle
Swept by emergency exit
Lineage
v3.2
Policy execution
Permanently halted — no signed execution can run again. Recovery remains available to the owner.

Every contract read and log query on this page is pinned to that one block, so the policy, the balances, and the event history describe the same moment. Nothing here is estimated or priced.

The deployed chain

drawn from this Zap's own policy fields, not from a template
Bound input1 0xZAPS — the exact amount the policy hash commits to.
0xDd90…CB07 ↗
ERC-20
Swap 0xZAPS → aeWETH through the allowlisted adapter, with no adapter calldata.
0x04f6…602C ↗
ERC-20
Owner
0x1733…4797 ↗
Recipient
0x1733…4797 ↗
Relayer fee cap
0 — no execution of this policy can pay a relayer fee.
Optimization
Enabled
Tracked assets
0x0Bd7…AD73 ↗0xDd90…CB07 ↗
Policy hash
Rehashes from the live policy fields.

The same block vocabulary the builder uses. A fork copies only the verified route, exact input and reproducible safety defaults; owner, recipient, nonce, executor and prior signatures never travel. Connectors are coloured by the shape of value moving along them.

What has happened

measured, not modelled
0Executions
0Of those, automated
1Emergency exits
None yetFirst execution
None yetLast execution

Produced by executions

None yet — this Zap has never emitted an execution log.

Fee withheld from output

Zero, and not because none happened to be taken. This policy commits maxRelayerFeeCap = 0, so no execution of it can pay a relayer fee. The bound comes from the policy hash, not from a measurement.

Stacked into 0xZAPS

None — no recurring-stack execution appears in this Zap's logs.

Swept by emergency exit

  • 1 0xZAPSreturned to the owner

Held right now

  • 0 aeWETH
  • 0 0xZAPS
  • 0 ETH
Custody balances at block 23,280,727. aeWETH, 0xZAPS, and ETH are the only balances this snapshot reads, so this is not a full inventory of what the Zap holds.

Counts and totals come only from this contract's own execution logs — Executed for an owner-signed run, ExecutedRecurring, ExecutedRecurringRelative, ExecutedRecurringStack and ExecutedTrigger for an automated one — plus its EmergencyExit logs. No USD value, token price, PnL, APY, or success rate appears on this page. A reverted execution emits no log at all, so a success rate computed from these logs would be unfalsifiable, and none is shown.

Every execution and exit

read from this contract's own logs

Executions

None yet.

Emergency exits

Exit1 0xZAPS to 0x1733…47970xebe0…41ee ↗Jul 30, 2026, 9:18 AM

Where this address came from

provenance
Created in block
23,046,697Jul 30, 2026, 4:59 AM
Creation transaction
0xef38f71b…80cd6a68 ↗
Owner at creation
0x1733…4797 ↗
CREATE2 salt
Implementation codehash
Factory implementation
0x5882…a987 ↗Factory version 3.2.0-candidate
Contract type
Automated · v3.2Can hold a recurring series whose live execution floor comes from an allowlisted price source, with an optional owner-signed slice stacked into 0xZAPS on every run.

This Zap is only on the site because the canonical factory's own ZapCreated log names it. An identically-shaped contract deployed by anything else would never reach this page.

Ask this capsule

answers cite the fields they rest on

Questions are answered only from what this capsule reports onchain. Any figure that does not appear in its own record is refused rather than guessed at.