← previous blocknext block →recent activity

Analyzing

Block #92,173,268

33 transactions · 22 stateful · 2026-08-01 10:02:22 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #92,173,268  ·  33 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x3de775b2…319b

0xa6afd3…d132

6 touches
3 conflicts

0x2385516f…eca5

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

4 touches
1 conflict

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x29c1a140…099f

0x34b655…2a6f

4 touches
1 conflict

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: Kuru Exchange: Market-WETH/USDC

3 conflicts on slot 0x3de775b20f…f1319b

← previous block·next block →recent activity