# How to read the proxy\_target of a proxy contract in a specific block height for example 23000000?

**URL:** <https://forum.fuel.network/t/how-to-read-the-proxy-target-of-a-proxy-contract-in-a-specific-block-height-for-example-23000000/8484>\
**Category:** General\
**Created:** [February 11, 2025, 3:01pm UTC](https://forum.fuel.network/t/how-to-read-the-proxy-target-of-a-proxy-contract-in-a-specific-block-height-for-example-23000000/8484 "2025-02-11T15:01:12Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![perseverance](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@perseverance](https://forum.fuel.network/u/perseverance)\
**Post date:** [February 11, 2025, 3:01pm UTC](https://forum.fuel.network/t/how-to-read-the-proxy-target-of-a-proxy-contract-in-a-specific-block-height-for-example-23000000/8484/1 "2025-02-11T15:01:12Z")

</div>

Hello, I have a question related to how to read proxy\_target of a proxy contract in a specific block height for example 23000000

Supposed that I have a proxy contract at address 0xe2815fb200736f50838bf1579cbdb1b591c39985b75442c8f91963760dc445b9 (this is an example address).

This is a proxy contract of Src14OwnedProxy type. I can read the proxy\_target to know the current implementation address of this contract.

The below typescript will help me to know the current proxy\_target at latest block. But I want to know the proxy\_target address at the specific block height, for example 23000000 that is 2 days ago. How to query that data?

I just want to know how to get that data. It can be done by typescript, Rust SDK or GraphQL still be ok. please help.

I am interested to know for Mainet.

```typescript
beforeEach(async () => {
        const provider = await Provider.create("https://mainnet.fuel.network/v1/graphql")

        let privateKey = process.env.FUEL_PRIVATE_KEY       

        const wallet_0 = Wallet.fromPrivateKey(privateKey, provider)
              
        const Proxy_ID = "0xe2815fb200736f50838bf1579cbdb1b591c39985b75442c8f91963760dc445b9"

        const proxyContract = new Src14OwnedProxy(Proxy_ID, wallet_0)             

        let tx = await proxyContract.functions.proxy_target().simulate()
        console.log("proxy_target: ", tx) 
        

    })

```

Thank you for your help.

---

<div class="post-metadata">

**Author:** ![naz3eh](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.fuel.network/naz3eh/32/2025_2.png) [@naz3eh](https://forum.fuel.network/u/naz3eh)\
**Post date:** [February 11, 2025, 10:09pm UTC](https://forum.fuel.network/t/how-to-read-the-proxy-target-of-a-proxy-contract-in-a-specific-block-height-for-example-23000000/8484/2 "2025-02-11T22:09:39Z")

</div>

Hey @perseverance, team has already implemented it. It will be available in the `fuel-core` `v0.42`, and the next step up SDKs to support this feature. though, you can try this feature by using the `fuel-core` from `master`, sync with state rewind enabled, and dry run any transaction in the past, using custom SDK

> <https://github.com/FuelLabs/fuel-core/pull/2661>
>
> Closes #2062
> 
> \## Description
> 
> Support dry running in past blocks. It's behin…d the \`--historical-execution\` flag.
> 
> \## Checklist
> \- \[x\] Breaking changes are clearly marked as such in the PR description and changelog
> \- \[x\] New behavior is reflected in tests
> \- \[x\] \[The specification\](https://github.com/FuelLabs/fuel-specs/) matches the implemented behavior (link update PR if changes are needed)
> 
> \### Before requesting review
> \- \[x\] I have reviewed the code myself
> \- \[x\] I have created follow-up issues caused by this PR and linked them here
> 
> \### After merging, notify other teams
> 
> \- \[\] \[Rust SDK\](https://github.com/FuelLabs/fuels-rs/)
> \- \[\] \[Platform documentation\](https://github.com/FuelLabs/devrel-requests/issues/new?assignees=&labels=new+request&projects=&template=NEW-REQUEST.yml&title=%5BRequest%5D%3A+) (for out-of-organization contributors, the person merging the PR will do this)

---

<div class="post-metadata">

**Author:** ![perseverance](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@perseverance](https://forum.fuel.network/u/perseverance)\
**Post date:** [February 12, 2025, 1:45pm UTC](https://forum.fuel.network/t/how-to-read-the-proxy-target-of-a-proxy-contract-in-a-specific-block-height-for-example-23000000/8484/3 "2025-02-12T13:45:48Z")

</div>

Thank you @naz3eh . It is nice feature to dryRun with past block. It is what I was looking for.

I was trying to try this feature with the Master branch.

But today I got a weird error:

> [@Cannot run the Fuel-core with mainnet ignition due to some weird error](https://forum.fuel.network/t/cannot-run-the-fuel-core-with-mainnet-ignition-due-to-some-weird-error/8494):
>
> I have followed the instruction to run the Mainnet [Node Operator | Fuel Docs](https://docs.fuel.network/docs/node-operator/fuel-ignition/mainnet-node/) But I got the weird error that Relayer cannot be started. Please help me. 2025-02-12T06:45:36.234958Z INFO fuel\_core\_bin::cli::run: 362: `[Importer, P2P, Producer, TxPool, GraphQL, GasPrice]` metrics are enabled 2025-02-12T06:45:36.251613Z INFO fuel\_core\_bin::cli::run: 398: Block production disabled 2025-02-12T06:45:36.251656Z WARN fuel\_core\_bin::cli::run: 459: The coinbase recipient `ContractId` is not set! 2025-0…

The error blocked me to try the feature. Please help also. Thank you very much.

---

<div class="post-metadata">

**Author:** ![perseverance](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@perseverance](https://forum.fuel.network/u/perseverance)\
**Post date:** [February 12, 2025, 2:57pm UTC](https://forum.fuel.network/t/how-to-read-the-proxy-target-of-a-proxy-contract-in-a-specific-block-height-for-example-23000000/8484/4 "2025-02-12T14:57:46Z")

</div>

Hi @naz3eh when the version fuel-core v0.42 will be available ?

Also I saw that there is the nightly version. I saw that it is still v0.41.6. Does the nightly include the merged pull-request?

---

<div class="post-metadata">

**Author:** ![perseverance](https://avatars.discourse-cdn.com/v4/letter/p/d6d6ee/32.png) [@perseverance](https://forum.fuel.network/u/perseverance)\
**Post date:** [February 15, 2025, 8:20am UTC](https://forum.fuel.network/t/how-to-read-the-proxy-target-of-a-proxy-contract-in-a-specific-block-height-for-example-23000000/8484/5 "2025-02-15T08:20:43Z")

</div>

Thank you very much. I was able to resolve the problem. Now I can try this feature.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/fuel/original/2X/5/57d5a345cc15a64b636e0d56e042857f8a0e80b1.png) [@system](https://forum.fuel.network/u/system)\
**Post date:** [March 8, 2025, 4:21am UTC](https://forum.fuel.network/t/how-to-read-the-proxy-target-of-a-proxy-contract-in-a-specific-block-height-for-example-23000000/8484/6 "2025-03-08T04:21:37Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.