Terra Classic transaction
6CCAAC9687793327DFE5611821C9DEC69F4364DA5FC68DB005705885A95E44FA
- Reported execution
- Success (code 0)
- Block
- 30765599
- Timestamp (UTC)
- 2026-10-09T19:47:07.000Z
- Gas used / wanted
- 4639957 / 44000000
Declared fees
Transaction fee fields, not a reconstruction of fee collection or payer balances.
- 35.2 USTC
- Declared gas limit
- 44000000
- 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 logs. 3 supported native legs retained of 3 parsed. At most 100 legs are retained.
| Asset | Exact amount | Sender wallet | Recipient wallet | Movement evidence | Message index |
|---|---|---|---|---|---|
 USTC | 35.2 | terra1a8wv7sex…k5ms63n4ux | terra17xpfvakm…8c5lkaeqfa
| Transaction fee | 0 |
 LUNC | 4,517.483695 | terra1jv65s3gr…9cd8pm7utl | terra1a8wv7sex…k5ms63n4ux | Transfer event | 1 |
| USTC | 14.02135 | terra1jv65s3gr…9cd8pm7utl |
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.
Contract-reported mints and burns
CW20-style token events reported by contracts in this transaction. Quantities retain exact raw units. These are not native LUNC or USTC burns, and they are not added to native burn totals.
0 supported events in the selected message logs.
No supported CW20-style mint or burn events were present in the selected representation.
Contract code, historical token decimals, balances, authority and ownership are not independently verified. Events do not establish before-and-after supply, redemption or destination-chain settlement. Each operation remains separate; no cross-contract total or inferred counterparty is shown.
Message types (11)
Declared messages describe attempted actions. Native movements and contract-reported token events are shown in the event panels above.
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
- /cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward
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 token events.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper108lmrztvc3pc3w774shgvpry4d3lf79k2ummna. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper120ppepaj2lh5vreadx42wnjjznh55vvktp78wk. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper14qv3eec9chk0d55ldjpffjwdet3wf4tdetqkk2. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper1e6w5qgzs5rzrz8ark25lagm2ga2h9n2tvgzpsl. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper1fjuvyccn8hfmn5r7wc2t3kwqy09zzp6tyjcf50. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper1hme9uynnxf0ga72xmwtdgztt2lmg0jlqjgsj5n. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper1mpmn2y9qw4dn6z2q3a7hy4c3wjztmvu7wz4r4u. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper1qfv3fyan5f4sylvnqzk9sxzlck823jy3a3dwg6. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper1qk46lk4kt4f90y4quv9mds0q26khhwdsjme29h. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper1s00gyl6dlz6gkfj0mwcrcffu8mrw8dgr9k3hkr. The message does not specify the amount paid.
- Staking reward withdrawal request by terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4ux for validator terravaloper1xl2ujgt7f6xn8v26rjkhy4f20x5plc3nq6nql7. The message does not specify the amount paid.
Declared research links
Open the accounts, validators and proposals named in supported message fields. These links do not establish signatures, ownership or completed actions. First 20 top-level messages only; unsupported or missing references are omitted. Multi-send recipient links are shown with their declared output rows.
Show 22 declared references
Message 1 · Declared delegator
terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4uxMessage 1 · Declared validator
terravaloper108lmrztvc3pc3w774shgvpry4d3lf79k2ummnaMessage 2 · Declared delegator
terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4uxMessage 2 · Declared validator
terravaloper120ppepaj2lh5vreadx42wnjjznh55vvktp78wkMessage 3 · Declared delegator
terra1a8wv7sexk4f09p38t7ercg8nr4zgk5ms63n4uxMessage 3 · Declared validator
terravaloper14qv3eec9chk0d55ldjpffjwdet3wf4tdetqkk2
Transaction memo
Empty memo.
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
- https://terra-classic-lcd.publicnode.com
- Public response provider
- https://terra-classic-lcd.publicnode.com
- Provider-reported response height
- 30947794
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.