WatchExplorechain 4663
← Deployed Zaps

0xfd73EF00D75B1e576402443385aca15D5127496A

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.

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
58,577,761
Snapshot taken
9/9/2026, 1:20:37 PM
Lifecycle
Executed
Lineage
v3.1
Policy execution
Unsupported on deployed v3.1; this runtime predates the one-way policy stop.

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 input0.001 aeWETH — the exact amount the policy hash commits to.
0x0Bd7…AD73
ERC-20
Swap aeWETH → 0xZAPS through the allowlisted adapter, with no adapter calldata.
0x04f6…602C
ERC-20
Owner
0x5a52…4aA2
Recipient
0x5a52…4aA2
Relayer fee cap
0 — no execution of this policy can pay a relayer fee.
Optimization
Enabled
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
2Executions
2Of those, automated
0Emergency exits
Jul 26, 2026, 5:13 PMFirst execution
Jul 26, 2026, 6:13 PMLast execution

Produced by executions

  • 1,999,853.214828 0xZAPSnet to the recipient · gross out of the adapter 2,020,053.752352 0xZAPS

Fee withheld from output

  • 20,200.537523 0xZAPSprotocol fee on automated runs — executor share plus lottery pot

Stacked into 0xZAPS

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

Swept by emergency exit

None — the owner has never pulled assets back out of this Zap.

Held right now

  • 0 aeWETH
  • 0 0xZAPS
  • 0 ETH
Custody balances at block 58,577,761. 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

AutoZap1,007,500.089768 0xZAPS to 0x5a52…4aA2 · protocol fee 10,176.768583 0xZAPSrun 2 · recurring · spot floor · submitted by 0x11DB…93470xe091…639f Jul 26, 2026, 6:13 PMAutoZap992,353.12506 0xZAPS to 0x5a52…4aA2 · protocol fee 10,023.76894 0xZAPSrun 1 · recurring · spot floor · submitted by 0x11DB…93470xa2e0…52f8 Jul 26, 2026, 5:13 PM

Emergency exits

None yet.

Where this address came from

provenance
Created in block
20,040,906Jul 26, 2026, 5:12 PM
Creation transaction
0xa2c7c94f…1f12233b
Owner at creation
0x5a52…4aA2
CREATE2 salt
Implementation codehash
Factory implementation
0x0fE5…1063Factory version 3.1.0-candidate
Contract type
Automated · v3.1Can hold a recurring series whose per-run floor is derived from an allowlisted price source at execution, or a one-shot price trigger. Any eligible executor may submit a run this Zap owes.

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.