fluxscan

A block explorer for the flux chain — a fully EVM-compatible network. Browse blocks, transactions, addresses, tokens, and NFTs. Verify smart contracts and track on-chain activity in real-time.

⌗

Blocks & Transactions

Browse every block and transaction on the flux chain with full detail views.

◇

Token Tracking

ERC-20 token transfers, holdings, and balances for any address.

□

NFT Support

ERC-721 and ERC-1155 transfer history across all collections.

✓

Contract Verification

Upload source code and ABI to verify deployed contracts.

Search

The search bar in the navigation accepts three types of input. Results redirect automatically to the matching detail page.

Block number Any integer — redirects to /block/{number}

Transaction hash 66-character hex string starting with 0x

Address 42-character hex string starting with 0x

If no match is found, you'll see a "No results" page. Search is case-insensitive for hex strings.

Address Pages

Each address page shows the on-chain balance (fetched live from the RPC node), total transaction count, and four tabbed views:

Transactions All transactions where this address is the sender or receiver. Paginated, sortable by block number.

Token Transfers ERC-20 token transfer events involving this address, with token name, symbol, and formatted amounts.

NFT Transfers ERC-721 and ERC-1155 transfer events showing token name, token ID, and quantity.

Token Holdings Calculated balances for all ERC-20 tokens this address holds (sum of inbound minus outbound transfers).

Each address also has a link to view or verify the contract at that address.

Tokens & NFTs

The explorer automatically indexes ERC-20, ERC-721, and ERC-1155 tokens from on-chain events. The Tokens page lists all discovered tokens with their name, symbol, total supply, and holder count.

Individual token pages show transfer history and, for NFT collections, individual token IDs and their transfer history.

detection Tokens are discovered from Transfer event logs. A token must have at least one transfer to appear in the explorer.

Contract Verification

You can verify a deployed smart contract by submitting its source code and ABI. Navigate to:

/contract/{address}

If the contract hasn't been verified yet, you'll see a verification form. Fill in:

Source Code The full Solidity source code (single file or flattened)

ABI The contract ABI as a JSON array

Compiler Version e.g. v0.8.20+commit.a1b79de6 (optional)

Optimization Whether optimization was enabled during compilation

Optimization Runs Number of optimization runs (default: 200)

Once verified, the contract page displays the source code and ABI in tabbed views.

Preparing Contracts for Verification

Before verifying, you need the source code and ABI from your compilation output.

1. Flatten your source

If your contract imports other files, flatten it into a single file. Most toolchains support this:

Hardhat

npx hardhat flatten contracts/MyContract.sol > flat.sol

Foundry

forge flatten src/MyContract.sol > flat.sol

solc

# If using imports, pass all source files:
solc --combined-json abi,bin MyContract.sol

2. Get the ABI

The ABI is generated during compilation. Extract it from your build output:

Hardhat

# After compilation, find it in:
cat artifacts/contracts/MyContract.sol/MyContract.json | jq '.abi'

Foundry

# After forge build:
cat out/MyContract.sol/MyContract.json | jq '.abi'

solc

solc --abi MyContract.sol

3. Note your compiler settings

Record the exact compiler version and optimization settings used during deployment. These are typically in your hardhat.config.js, foundry.toml, or the solc flags you passed.

tip The ABI must be valid JSON. If verification fails with an "invalid ABI" error, check that you're pasting the JSON array, not the entire artifact file.