Glossary

Learn the transaction, contract, storage, and debugging terms used throughout Skylens.

# Glossary

Learn the transaction, contract, storage, and debugging terms used throughout Skylens.

Skylens keeps product feature names in English so they match the interface. The definitions below explain how those terms are used in the documentation.

| Term            | Meaning in Skylens                                                                                                     |
| --------------- | ---------------------------------------------------------------------------------------------------------------------- |
| ABI             | The contract interface used to decode function names, inputs, outputs, and events.                                     |
| Bytecode        | EVM instructions deployed or executed by a contract. Use Bytecode Debugger when source or Source Maps are unavailable. |
| Call            | One contract execution frame inside a transaction, such as `CALL`, `STATICCALL`, or `DELEGATECALL`.                    |
| Execution Trace | The ordered tree of calls, events, errors, and state access produced while a transaction executes.                     |
| Implementation  | The contract that supplies code and Storage Layout for a proxy. It usually does not own the proxy's business state.    |
| Proxy           | A stable state-holding address that delegates execution to an implementation contract.                                 |
| Revert          | An EVM rollback that discards state changes in the reverted context. Gas already consumed is not restored.             |
| Source Map      | Compiler metadata that connects bytecode instructions to positions in source files.                                    |
| State Changes   | The persistent account and storage differences remaining after transaction execution.                                  |
| Storage         | Persistent EVM key-value state owned by a contract address.                                                            |
| Storage Layout  | Compiler metadata that maps Solidity variables and types to Storage Slots and byte offsets.                            |
| Storage Slot    | A 32-byte position in EVM Storage. Mappings and dynamic arrays derive data locations from base slots.                  |
| Token Flow      | A graph of asset transfer paths. It explains movement, while Balance Changes establishes final net impact.             |
| Virtual TestNet | An isolated network fork used to reproduce and modify a scenario without affecting the source chain.                   |

## Naming conventions

* Bold names such as **Execution Trace** and **Load Implementation** refer to visible Skylens interface labels.
* Code formatting such as `delegatecall`, `SSTORE`, and `slot0` refers to EVM operations, identifiers, or raw data.
* “Revert,” “rollback,” and “failed transaction” are related but not identical: a child call can revert without making the outer transaction fail.
* “Storage” describes persistent EVM state; “state” can also include balances, nonce, code, and other account data.

Skylens keeps product feature names in English so they match the interface. The definitions below explain how those terms are used in the documentation.

Term	Meaning in Skylens
ABI	The contract interface used to decode function names, inputs, outputs, and events.
Bytecode	EVM instructions deployed or executed by a contract. Use Bytecode Debugger when source or Source Maps are unavailable.
Call	One contract execution frame inside a transaction, such as `CALL`, `STATICCALL`, or `DELEGATECALL`.
Execution Trace	The ordered tree of calls, events, errors, and state access produced while a transaction executes.
Implementation	The contract that supplies code and Storage Layout for a proxy. It usually does not own the proxy's business state.
Proxy	A stable state-holding address that delegates execution to an implementation contract.
Revert	An EVM rollback that discards state changes in the reverted context. Gas already consumed is not restored.
Source Map	Compiler metadata that connects bytecode instructions to positions in source files.
State Changes	The persistent account and storage differences remaining after transaction execution.
Storage	Persistent EVM key-value state owned by a contract address.
Storage Layout	Compiler metadata that maps Solidity variables and types to Storage Slots and byte offsets.
Storage Slot	A 32-byte position in EVM Storage. Mappings and dynamic arrays derive data locations from base slots.
Token Flow	A graph of asset transfer paths. It explains movement, while Balance Changes establishes final net impact.
Virtual TestNet	An isolated network fork used to reproduce and modify a scenario without affecting the source chain.

Naming conventions

Bold names such as Execution Trace and Load Implementation refer to visible Skylens interface labels.
Code formatting such as delegatecall, SSTORE, and slot0 refers to EVM operations, identifiers, or raw data.
“Revert,” “rollback,” and “failed transaction” are related but not identical: a child call can revert without making the outer transaction fail.
“Storage” describes persistent EVM state; “state” can also include balances, nonce, code, and other account data.

Getting Started

Quickly understand what happened in a transaction, from its outcome to its execution.

Balance Changes

See the net change in native assets, tokens, and NFTs for every address.

On this page

Naming conventions