← previous blocknext block →recent activity

Analyzing

Block #94,307,269

17 transactions · 16 stateful · 2026-08-08 21:04:39 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

1.18

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #94,307,269  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x94ec7ec8…8057

0xa6afd3…d132

8 touches
6 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

8 touches
6 conflicts

0x66bdb4c2…7ea6

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x4c1fbdf6…953d

0x754704…b603

4 touches
1 conflict

0x595233b5…c4aa

0x754704…b603

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

15 conflicts on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity