[BUG] eth_blockReceipts error response on block : 0x74c95cf

[qn-srikanth]

Seid version

name: sei
server_name: <appd>
version: v6.0.1-hotfix-rpc-3
commit: 40be6ab8084cc668a17edf3fe66c9d7695f1acdb
build_tags: netgo,
go: go version go1.21.13 linux/amd64
build_deps:
- cosmossdk.io/errors@v1.0.0
- filippo.io/edwards25519@v1.0.0-rc.1
- github.com/99designs/keyring@v1.2.1

Chain ID
Sei Pacific - 1329

Describe the bug

Block = 0x74c95cf = 122459599

{"method":"eth_getBlockReceipts","params":["0x74c95cf"],"id":1,"jsonrpc":"2.0"}

{"jsonrpc":"2.0","id":1,"error":{"code":-32000,"message":"failed to find transaction in block"}}

To Reproduce

curl https://sei.public-rpc.com \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"method":"eth_getBlockReceipts","params":["0x74c95cf"],"id":1,"jsonrpc":"2.0"}'

Expected behavior
Non-error response for block : 122459599

Screenshots

---

If applicable, add screenshots to help explain your problem.

[QN-Ben]

eth_getBlockReciepts returning incorrect blockNumber responses for block 0x761A36D

curl https://docs-demo.sei-pacific.quiknode.pro/ \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"method":"eth_getBlockReceipts","params":["0x761A36D"],"id":1,"jsonrpc":"2.0"}' | jq | grep blockNumber

Response:

      "blockNumber": "0x761a36d",
          "blockNumber": "0x761a36d",
          "blockNumber": "0x761a36d",
          "blockNumber": "0x761a36d",
          "blockNumber": "0x761a36d",
      "blockNumber": "0x761a36d",
      "blockNumber": "0x761a36d",
      "blockNumber": "0x761a370",
      "blockNumber": "0x761a370",
      "blockNumber": "0x761a370",
          "blockNumber": "0x761a370",
          "blockNumber": "0x761a370",
      "blockNumber": "0x761a370",
      "blockNumber": "0x761a370",
          "blockNumber": "0x761a370",
          "blockNumber": "0x761a370",
      "blockNumber": "0x761a370",
      "blockNumber": "0x761a370",
          "blockNumber": "0x761a370",
          "blockNumber": "0x761a370",
      "blockNumber": "0x761a36d",
      "blockNumber": "0x761a370",

[qn-srikanth]

Both these issues have already been resolved with v6.0.1-hotfix-rpc-9