← previous blocknext block →recent activity

Analyzing

Block #94,301,134

16 transactions · 16 stateful · 2026-08-08 20:33:33 UTC

Parallelism

56/100

Blocked

63%

Avg conflicts / tx

1.69

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #94,301,134  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x11b69a7e…334e

0xee8c0e…1242

14 touches
21 conflicts

0xa1087a5c…66c4

0x754704…b603

14 touches
21 conflicts

0xae170c4b…f13c

0xa6afd3…d132

8 touches
6 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

8 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

6 touches
3 conflicts

0x5a05509d…d073

0x34b655…2a6f

6 touches
3 conflicts

0xb4e0a934…5fc7

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: Wrapped Ether (WETH)

21 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity