Terra Classic transaction
835E798FFC73CE67BA03090E854D0CB5BA902DA04C1A78797E125C18806FC701
- Reported execution
- Success (code 0)
- Block
- 30768416
- Timestamp (UTC)
- 2026-10-10T00:25:00.000Z
- Gas used / wanted
- 101111 / 300000
Declared fees
Transaction fee fields, not a reconstruction of fee collection or payer balances.
No fee coins recorded in the returned fee field.
- Declared gas limit
- 300000
- Declared fee payer
- Empty payer field; signer address not resolved here.
- Declared fee granter
- Empty granter field; no fee grant requested in this field.
These are declarations in the returned transaction. A granter names a requested fee grant; it does not prove a grant existed or paid. The declared gas limit is separate from reported gas wanted and gas used. These fields do not establish signer identity, actual debits, tax, refunds or burns.
Executed LUNC and USTC movements
Native transfer events are interpreted when successful execution is established. A transaction can contain several legs, including fees, tax and module routing.
Event source: Structured events. 0 supported native legs retained of 0 parsed. At most 100 legs are retained.
No supported LUNC or USTC transfer legs were recorded in the selected event representation.
Movement interpretation and limits
This interprets LUNC and USTC native transfer events, using one event representation to avoid double counting. Other denominations, CW20 transfers and every contract effect are not decoded. Missing or conflicting evidence remains partial or unavailable.
Tax and fee labels require executed payment evidence. Module routing does not establish a burn, and a wallet address does not establish its owner. Leg totals are not unique trading volume or a change in supply. These movements are distinct from the declared message requests and fee fields.
Message indexes are zero based. The transaction block and UTC time above apply to these rows. All six native-token decimal places are retained before display.
Contract-reported transfers
CW20-style transfer events from this transaction. Quantities retain their exact raw units. Contract code, historical token decimals, balances and wallet ownership are not independently verified by these events.
0 supported events in the selected message logs.
No supported CW20-style transfer events were present in the selected event representation.
Addresses identify roles reported by the contract. Repeated operations remain separate; quantities are not added across token contracts. This view covers transfers and sends, including allowance actions. Token creation, token burns and other contract effects remain outside this view.
Message types (2)
Declared messages describe attempted actions. Native movements and contract-reported transfers are shown in the event panels above.
- /terra.oracle.v1beta1.MsgAggregateExchangeRateVote
- /terra.oracle.v1beta1.MsgAggregateExchangeRatePrevote
What the messages request
These summaries interpret declared top-level fields. They describe requests, not proof of completed transfers or account ownership. The event panels above show supported native movements and contract-reported transfers.
- This message type is not interpreted here. Consult its source record in Finder.
- This message type is not interpreted here. Consult its source record in Finder.
Transaction memo
@classic-terra/oracle-feeder@3.1.5
Memos are untrusted sender-supplied text; they do not verify an identity or claim.
Source: configured Terra Classic LCD transaction record (columbus-5). Successful source read . This is a source observation, not independent consensus verification. Linked block coverage may be incomplete.
Transaction response provenance
- Public requested provider
- Withheld or unavailable
- Public response provider
- Withheld or unavailable
- Provider-reported response height
- 30846475
This evidence belongs to the original successful source read shown above. Cached or stale records retain that response's provider and height fields. A response height is separate from the transaction's inclusion block; it does not independently verify chain state or execution.
Only recognized public provider origins are displayed. Missing or withheld provider evidence does not make the transaction's fields independently verified.