0x1e5141d3d83faeec635a14121711397b806f43661c01ede74705629255c56aaa
Reference record
This transaction left a record that someone consulted this volume. One datatoken was minted, handed to the caller, and burned within the same transaction. What remains is not the datatoken but the record of the reference.
A reference record says nothing about whether the text is intact. Anyone can trigger one for free, so a high count means nothing. Whether the text was altered is settled by the root instead.
What happened
The 6 records in the order the chain wrote them. The number on the left is the index within the block, the same number Etherscan shows.
- 80Transfermintzero address→0x2720…893c1 datatoken
One datatoken was newly minted. A sender of the zero address is the marker for "newly created".
- 81TokensDispensed
The Dispenser recorded that it handed one out. The Dispenser is a shared Ocean contract, not something built for this material.
- 82Transfermove0x2720…893c→0xffa5…ea0b1 datatoken
That same one moved to its next holder.
- 83OrderStarted
This is the line that matters. The record that this version was consulted is left in a form nobody can erase. The other entries are the procedure that leaves this one line.
- 84ProviderFee
Every provider fee field is zero. Ocean normally verifies a provider signature before an order goes through, but with the fee address set to zero, the address recovered from an empty signature is also zero, so the two match. That is why no Ocean node has to run at all.
- 85Transferburn0xffa5…ea0b→zero address1 datatoken
The datatoken was burned. A recipient of the zero address is the marker for "gone". It was held only for a few log entries inside this same transaction.
Read from the chain
None of these are claims. They are values the chain itself holds.
0xffa5e5258de73d6356e65b3eaa036392aa06ea0bWho 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.
buyFromDispenserAndOrderDerived 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.
0xffa5e5258de73d6356e65b3eaa036392aa06ea0bEtherscan0x7912e01939812be315f1f449ae20ce2515671f5bexplained here0x2720d405ef7cdc8a2e2e5aebc8883c99611d893cexplained here
The raw screen
The unannotated screen is here, to read alongside the notes above.