> For the complete documentation index, see [llms.txt](https://champlify-labs-llc.gitbook.io/ssow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://champlify-labs-llc.gitbook.io/ssow/whale-shadows/how-to-obtain/block-explorer.md).

# Via Block Explorer

For technical users who prefer direct contract interaction, you can sync your Whale Shadows by interacting with the Beacon or Shadow contracts using block explorers.

## Contract Addresses

### ApeChain

* **Shadow NFT Contract:** `0x3C3E92B627a817832DEd520Da5640246c9AAAF65`
* **Beacon Contract:** `0xFAa821786E367057F36BCdD045E3864437Fd9344`
* **Block Explorer:** [ApeScan](https://apescan.io)

### Abstract

* **Shadow NFT Contract:** `0x7F283cB49724c3f592AF1DB8De400091ACB9Cf6f`
* **Beacon Contract:** `0x2118215ecdEED213aDC809786bf95F3Bfe0b8EE5`
* **Block Explorer:** [Abscan](https://abscan.org)

### Ethereum (Source Chain)

* **OG Whale Collection:** `0x88091012eedf8dba59d08e27ed7b22008f5d6fe5`
* **Beacon Contract:** `0xFAa821786E367057F36BCdD045E3864437Fd9344`
* **ExclusiveDelegateResolver:** `0x0000000000007129AF73C46C9F01a3fB4FF61A02`
* **Block Explorer:** [Etherscan](https://etherscan.io)

> **Note:** The Beacon contract is the core of the Shadows infrastructure. It uses LayerZero technology and delegate.xyz contracts to determine the ownership of your OG Ethereum whale and controls the corresponding Shadow NFTs across all supported chains.

## Syncing Methods

Shadows can be synced using either contract type, each with different approaches and use cases:

### Using the Beacon Contract

**Best for: Advanced users, developers, and those wanting maximum control**

The Beacon contract provides direct control over the Shadow ecosystem and can trigger updates across multiple chains. This method offers more granular control but requires more technical parameters.

**Pros:**

* Maximum control and flexibility
* Can specify custom gas limits and refund recipients
* Direct access to the core Shadow infrastructure
* Suitable for programmatic/contract interactions

**Cons:**

* More complex parameter setup (5 parameters + payableAmount required)
* Requires knowledge of the base collection address
* More technical complexity

For detailed instructions on interacting with the Beacon contract, see [Beacon Contract](https://github.com/champlification/ssow-docs/blob/main/docs/whale-shadows/how-to-obtain/beacon-contract.md).

### Using the Shadow Contract

**Best for: Most users and simpler interactions**

The Shadow contract provides a simplified interface that internally calls the Beacon contract. This is the approach recommended by 0xQuit in most user guides and offers the easiest user experience.

**Pros:**

* Simplified interface (only 2 parameters + payableAmount: tokenIds, eids, and LayerZero fee)
* Easier for non-technical users
* Automatic handling of most technical details
* Matches the approach shown in 0xQuit's tutorials

**Cons:**

* Less control over advanced options
* Still requires separate transactions on each chain

For detailed instructions on interacting with Shadow contracts, see [Shadows Contract](https://github.com/champlification/ssow-docs/blob/main/docs/whale-shadows/how-to-obtain/shadows-contract.md).

Both methods achieve the same result: ensuring your Shadows accurately reflect the current ownership of your OG Whale on Ethereum. **Most users should start with the Shadow Contract method** for its simplicity, while developers and advanced users may prefer the Beacon Contract for its additional control options.