Event signature · NFT sales, names and staking

OrderFulfilled (Seaport) event signature and topic0

The topic0 of the OrderFulfilled (Seaport) event is 0x9d9af8e38d66c62e2c12f0225249fd9d721c54b83f48d9352c97c6cacdcb6f31, the keccak-256 hash of OrderFulfilled(bytes32,address,address,address,(uint8,address,uint256,uint256)[],(uint8,address,uint256,uint256,address)[]); 2 of its 6 arguments are indexed. Marketplace sale settled through Seaport (OpenSea and compatible).

Anatomy of a OrderFulfilled (Seaport) log

Topics

  • topic00x9d9af8e38d66c62e2c12f0225249fd9d721c54b83f48d9352c97c6cacdcb6f31keccak256("OrderFulfilled(bytes32,address,address,address,(uint8,address,uint256,uint256)[],(uint8,address,uint256,uint256,address)[])")
  • topic1offerer (address)indexed: filterable
  • topic2zone (address)indexed: filterable

Data

  • dataorderHash (bytes32), recipient (address), offer ((uint8,address,uint256,uint256)[]), consideration ((uint8,address,uint256,uint256,address)[])ABI-encoded, decoded with the ABI
Parameters

Arguments and where they sit in the log

Indexed arguments travel as topics and can be filtered cheaply; the others are ABI-encoded together in the data.

NameTypeIn the log
orderHashbytes32data
offereraddresstopic1
zoneaddresstopic2
recipientaddressdata
offer(uint8,address,uint256,uint256)[]data
consideration(uint8,address,uint256,uint256,address)[]data

Solidity declaration

event OrderFulfilled(bytes32 orderHash, address indexed offerer, address indexed zone, address recipient, (uint8,address,uint256,uint256)[] offer, (uint8,address,uint256,uint256,address)[] consideration);

Canonical signature

OrderFulfilled(bytes32,address,address,address,(uint8,address,uint256,uint256)[],(uint8,address,uint256,uint256,address)[])

topic0

0x9d9af8e38d66c62e2c12f0225249fd9d721c54b83f48d9352c97c6cacdcb6f31

Ready-made alerts

Get an alert on OrderFulfilled

Each rule opens with the contract and the conditions filled in. Sign in, pick your chat and click Create.

Who emits it

Contracts we list that emit OrderFulfilled

Any other contract with the same signature emits a log with the same topic0.

Code

Read OrderFulfilled logs in code

The same filter in viem, ethers and plain JSON-RPC, and the Solidity that emits it. The address is Seaport 1.6 (OpenSea), a contract we list that emits it.

viem
import { createPublicClient, http, parseAbiItem } from "viem"
import { mainnet } from "viem/chains"

const client = createPublicClient({ chain: mainnet, transport: http() })

const logs = await client.getLogs({
  address: "0x0000000000000068f116a894984e2db1123eb395",
  event: parseAbiItem("event OrderFulfilled(bytes32 orderHash, address indexed offerer, address indexed zone, address recipient, (uint8,address,uint256,uint256)[] offer, (uint8,address,uint256,uint256,address)[] consideration)"),
  fromBlock: "latest",
})

for (const log of logs) console.log(log.args) // { orderHash, offerer, zone, recipient, offer, consideration }
ethers v6
import { Interface, JsonRpcProvider } from "ethers"

const provider = new JsonRpcProvider(process.env.RPC_URL)
const iface = new Interface(["event OrderFulfilled(bytes32 orderHash, address indexed offerer, address indexed zone, address recipient, (uint8,address,uint256,uint256)[] offer, (uint8,address,uint256,uint256,address)[] consideration)"])

const logs = await provider.getLogs({
  address: "0x0000000000000068f116a894984e2db1123eb395",
  topics: [iface.getEvent("OrderFulfilled")!.topicHash],
})

for (const log of logs) console.log(iface.parseLog(log)?.args)
JSON-RPC (eth_getLogs)
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getLogs",
  "params": [
    {
      "address": "0x0000000000000068f116a894984e2db1123eb395",
      "topics": [
        "0x9d9af8e38d66c62e2c12f0225249fd9d721c54b83f48d9352c97c6cacdcb6f31"
      ],
      "fromBlock": "latest"
    }
  ]
}
Solidity
event OrderFulfilled(bytes32 orderHash, address indexed offerer, address indexed zone, address recipient, (uint8,address,uint256,uint256)[] offer, (uint8,address,uint256,uint256,address)[] consideration);

// inside a function:
emit OrderFulfilled(orderHash, offerer, zone, recipient, offer, consideration);
Example

An example OrderFulfilled log, encoded and decoded

Placeholder values, not a real transaction: how each argument is stored in the topics and the data, and what decoding gives back.

Encoded (as the node returns it)
  • topic0keccak256("OrderFulfilled(bytes32,address,address,address,(uint8,address,uint256,uint256)[],(uint8,address,uint256,uint256,address)[])")0x9d9af8e38d66c62e2c12f0225249fd9d721c54b83f48d9352c97c6cacdcb6f31
  • topic1offerer0x0000000000000000000000002222222222222222222222222222222222222222
  • topic2zone0x0000000000000000000000003333333333333333333333333333333333333333
  • data0xabababababababababababababababababababababababababababababababab0000000000000000000000004444444444444444444444444444444444444444000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000500000000000000000000000066666666666666666666666666666666666666660000000000000000000000000000000000000000000000000000000000001b580000000000000000000000000000000000000000000000000000000000001f400000000000000000000000000000000000000000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000600000000000000000000000077777777777777777777777777777777777777770000000000000000000000000000000000000000000000000000000000001f4000000000000000000000000000000000000000000000000000000000000023280000000000000000000000001111111111111111111111111111111111111111
Decoded with the ABI
  • orderHashbytes320xabababababababababababababababababababababababababababababababab
  • offereraddress · indexed0x2222222222222222222222222222222222222222
  • zoneaddress · indexed0x3333333333333333333333333333333333333333
  • recipientaddress0x4444444444444444444444444444444444444444
  • offer(uint8,address,uint256,uint256)[][[5, 0x6666666666666666666666666666666666666666, 7000, 8000]]
  • consideration(uint8,address,uint256,uint256,address)[][[6, 0x7777777777777777777777777777777777777777, 8000, 9000, 0x1111111111111111111111111111111111111111]]
FAQ

Frequently asked questions

What is the topic0 of the OrderFulfilled (Seaport) event?

0x9d9af8e38d66c62e2c12f0225249fd9d721c54b83f48d9352c97c6cacdcb6f31: the keccak-256 hash of OrderFulfilled(bytes32,address,address,address,(uint8,address,uint256,uint256)[],(uint8,address,uint256,uint256,address)[]).

Which OrderFulfilled (Seaport) arguments are indexed?

offerer, zone are indexed and sit in the log's topics; orderHash, recipient, offer, consideration are in the data.

How do I get an alert when a contract emits OrderFulfilled (Seaport)?

Open one of the ready-made rules on this page, or add any contract and pick OrderFulfilled (Seaport) from the event list. Conditions can be set on indexed and non-indexed arguments, and each alert names the contract and links to the transaction.

Keep exploring

More event signatures and tools

Know the moment a contract emits it

The Beta plan is free: one wallet and one contract, no credit card.