Starknet / block
Starknet block lookup
Look up any Starknet block on Voyager. tx.taxi detects the format, picks the right Starknet explorer, and redirects.
Starknet is a ZK-rollup that settles to Ethereum and uses its own Cairo-based VM, so its address format is not EVM-compatible. Starknet addresses are field elements smaller than 2^252, written as 0x-prefixed hex of up to 63 characters - shorter than an Ethereum address by 1 hex digit, but otherwise similar in shape. Transaction hashes use the same field-element form. Paste any Starknet value at tx.taxi/{value} and the router recognises the Starknet format and 302-redirects you to the matching Voyager page. Voyager is tx.taxi's configured Starknet explorer and displays both L2 activity and the L1 settlement state. On this page: Starknet block lookups specifically.
How it works
- Copy your
Starknet block(e.g. a block height or hash). - Paste into the search above or visit
tx.taxi/<your-block>directly. - tx.taxi detects the Starknet format and redirects to Voyager.
Frequently asked questions
How long is a Starknet address?
A Starknet address is a field element less than 2^252. Written as 0x-prefixed hex, it is up to 63 hex characters long - one less than a 64-hex Ethereum 32-byte value. Leading zeros are commonly omitted.
Are Starknet addresses the same as Ethereum addresses?
No. Starknet uses Cairo and its own STARK-friendly field, not the Ethereum EVM. An address valid on Starknet is not generally valid on Ethereum L1, even if both are written as 0x-prefixed hex.
What does Voyager show for a Starknet transaction?
Voyager displays the transaction status, the calls inside it (Starknet supports multi-call transactions by default), events emitted, and the corresponding L1 settlement state once the block has been proved and submitted to Ethereum.