EVM ยท 3ULL

PLAYA3ULL Games block explorer

Look up PLAYA3ULL Games addresses, transactions, and blocks - routed live to Avascan.

PLAYA3ULL Games is an Avalanche L1 subnet routed by tx.taxi through the avalanche-c parent. The PLAYA3ULL Games L1 is EVM-compatible, so addresses use the standard 42-character 0x-prefixed hex format and transaction hashes are 0x-prefixed 64-character hex strings, identical to anything you would paste against Ethereum. Paste a 3ULL-related value at tx.taxi/{value} and the router classifies it through the EVM regex layer, probes the avalanche-c parent to confirm the match, then 302-redirects to the Avascan entry pinned for the PLAYA3ULL Games L1. Avascan is the configured explorer for every Avalanche L1 wired into tx.taxi.

Lookup PLAYA3ULL Games by type

PLAYA3ULL Games explorers

Category
evm
Native symbol
3ULL
Configured explorers
1
Object types
address, tx, block

Live examples

Try a real PLAYA3ULL Games lookup. tx.taxi will route it straight to the configured explorer.

Frequently asked questions

What does a PLAYA3ULL Games address look like?

PLAYA3ULL Games runs as an EVM Avalanche L1, so an address is 42 characters: '0x' followed by 40 hex digits. Native gas on the PLAYA3ULL Games L1 is paid in 3ULL, and the same address format covers wallets and contracts.

Which explorer is wired up for PLAYA3ULL Games?

tx.taxi pins PLAYA3ULL Games (3ULL) lookups to Avascan, the configured Avalanche-ecosystem explorer for this L1. The PLAYA3ULL Games-specific Avascan path resolves addresses, tx hashes, and block heights with one routing rule.

Is PLAYA3ULL Games EVM-compatible?

Yes. PLAYA3ULL Games is registered in tx.taxi as an EVM Avalanche L1 under the avalanche-c parent, meaning 3ULL lookups share Ethereum's hex shapes and pass through the EVM classifier.

Related