Terra Classic transaction
824A5C52F653E3171D12590FFC444AD609637A6157F0AD4BC5B04BD162C61BF4
- Reported execution
- Success (code 0)
- Block
- 31104929
- Timestamp (UTC)
- 2026-11-02T04:10:15.000Z
- Gas used / wanted
- 13775686 / 15148252
Declared fees
Transaction fee fields, not a reconstruction of fee collection or payer balances.
- 429.074238 LUNC
- Declared gas limit
- 15148252
- 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. 19 supported native legs retained of 19 parsed. At most 100 legs are retained.
| Asset | Exact amount | Sender wallet | Recipient wallet | Movement evidence | Message index |
|---|---|---|---|---|---|
 LUNC | 429.074238 | terra1p076w9h4…x7payvmnew | terra17xpfvakm…8c5lkaeqfa
| Transaction fee | 0 |
| LUNC | 98.103263 | terra1jv65s3gr…9cd8pm7utl | terra1y5al0sph…w7qmpmfqpn | Transfer event | 0 |
 USTC | 0.296873 | 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 (1)
Declared messages describe attempted actions. Native movements and contract-reported token events are shown in the event panels above.
- /cosmos.authz.v1beta1.MsgExec
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.
- Authz execution request: declared grantee terra1p076w9h4z76jy65ydll7petl89x2x7payvmnew; 9 nested message declarations. Authorization, grant state, signatures and completed effects are not established.
Nested authorization requests
Authorization unverified · Decode details
These are declared MsgExec requests, not proof of a grant or completed action. Up to 20 nested declarations across the first 20 top-level messages are shown, expanding one wrapper. Grant state, signatures, signer identity and resulting effects are not checked. Further nested wrappers and contract instructions remain opaque.
Authorization request · message 1
Declared grantee: terra1p076w9h4z76jy65ydll7petl89x2x7payvmnew
Nested requests: 9
Nested request 1 · /cosmos.staking.v1beta1.MsgDelegate
Delegation request: 98.103255 LUNC; delegator terra1y5al0sphwmu89un2gyat2g5yskw8w7qmpmfqpn; validator terravaloper1xjlc2jl4nyywuwgttkcjqjgxxdkafqrexd7e9l.
Nested request 2 · /cosmos.staking.v1beta1.MsgDelegate
Delegation request: 13.984166 LUNC; delegator terra184fd3jnkgfztj680tyeld0gvdv8tkmmdk9888z; validator terravaloper1xjlc2jl4nyywuwgttkcjqjgxxdkafqrexd7e9l.
Nested request 3 · /cosmos.staking.v1beta1.MsgDelegate
Delegation request: 185.473934 LUNC; delegator terra1the7wgp7fkf6ftmgjfp2v6gw9r06f5ms9rrx4a; validator terravaloper1xjlc2jl4nyywuwgttkcjqjgxxdkafqrexd7e9l.
Remaining nested requests (6)
Nested request 4 · /cosmos.staking.v1beta1.MsgDelegate
Delegation request: 550.567422 LUNC; delegator terra1ds5xyeg3p4pvft005yns98adygzuh4v8ps5jdz; validator terravaloper1xjlc2jl4nyywuwgttkcjqjgxxdkafqrexd7e9l.
Nested request 5 · /cosmos.staking.v1beta1.MsgDelegate
Delegation request: 1137.400327 LUNC; delegator terra1kd9w839acyq5ve05y22ednac4ngfg8ww6my4pw; validator terravaloper1xjlc2jl4nyywuwgttkcjqjgxxdkafqrexd7e9l.
Transaction memo
REStaked by 🔥Play to burn - ♥️♣️TerraCasino♦️♠️
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
- 31106014
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.