`0x22E5338E9eabc6e69929c4879f1B8ACdeeB03776`

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 block✓ 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: 20,994,144
Snapshot taken: 7/27/2026, 7:48:23 PM
Lifecycle: Executed

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

Settle0xZAPS to 0x1733…4797.

0x1733…4797 ↗

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. Connectors are coloured by the shape of value moving along them.

What has happened

measured, not modelled

2Executions

0Emergency exits

Jul 25, 2026, 6:24 PMFirst execution

Jul 25, 2026, 6:25 PMLast execution

Produced by executions

2,128,356.790597 0xZAPSnet to the recipient · gross out of the adapter 2,128,356.790597 0xZAPS

Relayer fee taken

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.

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 20,994,144. 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 Executed and 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

Executed1,064,143.802638 0xZAPS to 0x1733…4797nonce 378248…04210xcda0…9ef6 ↗Jul 25, 2026, 6:25 PM Executed1,064,212.987958 0xZAPS to 0x1733…4797nonce 741747…22950x338c…d10d ↗Jul 25, 2026, 6:24 PM

Emergency exits

None yet.

Where this address came from

provenance

Created in block: 19,222,814Jul 25, 2026, 6:24 PM
Creation transaction: 0x02bd5398…adcbafbd ↗
Owner at creation: 0x1733…4797 ↗
CREATE2 salt
Implementation codehash
Factory implementation: 0x2a5E…E11A ↗Factory version 1.1.0
Contract type: One-shotExecutes its frozen policy once, against an owner-signed intent.

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.