← previous blocknext block →recent activity

Analyzing

Block #93,359,291

24 transactions · 19 stateful · 2026-08-05 13:30:10 UTC

Parallelism

88/100

Blocked

32%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #93,359,291  ·  24 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x2385516f…eca5

0x34b655…2a6f

4 touches
1 conflict

0x2504936d…39f3

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8a1f78fd…b178

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 0x56a919c43e…27ab49

← previous block·next block →recent activity