← previous blocknext block →recent activity

Analyzing

Block #94,202,211

26 transactions · 24 stateful · 2026-08-08 12:12:15 UTC

Parallelism

69/100

Blocked

38%

Avg conflicts / tx

1.19

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #94,202,211  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xa1087a5c…66c4

0x754704…b603

16 touches
28 conflicts

0x0778475b…bd75

0x2a68ba…90c5

12 touches
15 conflicts

0x3cb8fcab…f1dc

0x065c9d…c394

12 touches
15 conflicts

0x0629cebb…4e45

0x34b655…2a6f

6 touches
3 conflicts

0x1d9867ad…6d9a

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

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: USDC (USDC)

28 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity