← previous blocknext block →recent activity

Analyzing

Block #94,319,133

16 transactions · 15 stateful · 2026-08-08 22:04:53 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,319,133  ·  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

0x5df7cf2b…bbe5

0x34b655…2a6f

4 touches
1 conflict

0x66bdb4c2…7ea6

0x34b655…2a6f

4 touches
1 conflict

0x6f97afda…faec

0x34b655…2a6f

4 touches
1 conflict

0x7abc2f28…1a11

0x34b655…2a6f

4 touches
1 conflict

0xb81d9f8e…c733

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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