Readonly
addressReadonly
blockThe block hash of the block this log occurred in. Use the [[Log-getBlock]] to get the [[Block]].
Readonly
blockThe block number of the block this log occurred in. It is preferred to use the [[Block-hash]] when fetching the related [[Block]], since in the case of an orphaned block, the block at that height may have changed.
Readonly
dataThe data included in this log when it was emitted.
Readonly
fragmentThe matching event.
Readonly
indexThe index within the block this log occurred at. This is generally not useful to developers, but can be used with the various roots to proof inclusion within a block.
Readonly
interfaceThe Contract Interface.
Readonly
providerThe provider connected to the log used to fetch additional details if necessary.
Readonly
removedIf the Log represents a block that was removed due to an orphaned block, this will be true.
This can only happen within an orphan event listener.
Readonly
topicsThe indexed topics included in this log when it was emitted.
All topics are included in the bloom filters, so they can be efficiently filtered using the [[Provider-getLogs]] method.
Readonly
transactionThe transaction hash of the transaction this log occurred in. Use the [[Log-getTransaction]] to get the [[TransactionResponse]].
Readonly
transactionThe index within the transaction of this log.
The address of the contract that emitted this log.