0xa7c968871264e63510a25f44a23f5d656737278baae5b56294315fab25afa761
Metadata record
This transaction wrote the volume metadata (DDO) onto the chain. It is not encrypted, so reading it needs no server.
In August 2026 all 55 records were rewritten to take the publisher name out of the metadata. The earlier versions carrying the name remain on the chain. They cannot be removed.
What happened
The 1 records in the order the chain wrote them. The number on the left is the index within the block, the same number Etherscan shows.
- 20MetadataUpdated
The metadata was rewritten. The earlier version remains; nothing can be removed from the chain.
What was written
Rewriting does not remove the previous version. Nothing can be deleted from the chain.
0x000x00 marks it as not encrypted, which is why reading it needs no server.
Read from the chain
None of these are claims. They are values the chain itself holds.
0xa787b1285d7d0cf5284167ce278774371946a3aaWho paid the gas. This can differ from the consumer named in the record — anyone can name someone else as the consumer.
The contract this transaction spoke to.
setMetaDataDerived from the first four bytes of the call data. Etherscan sometimes leaves it as hex.
Zero. A datatoken has no price.
Goes to the validator that built the block. It is not payment for the datatoken.
Addresses involved
Addresses this catalogue can explain link inward. The rest link out to Etherscan.
0xa787b1285d7d0cf5284167ce278774371946a3aaEtherscan0x26f4b452cd1df9a66751bbd9998570e3b271a062explained here
The raw screen
The unannotated screen is here, to read alongside the notes above.