← previous blocknext block →recent activity

Analyzing

Block #94,134,259

16 transactions · 11 stateful · 2026-08-08 06:27:54 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #94,134,259  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x320701d5…f9f3

0x34b655…2a6f

4 touches
1 conflict

0x320701d5…f9f4

0x34b655…2a6f

4 touches
1 conflict

0x41c66186…229a

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x8d5fc820…1750

0x34b655…2a6f

4 touches
1 conflict

0xa9a9d0e0…4087

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

1 conflict on slot 0x11b69a7ea1…83334e

← previous block·next block →recent activity