← previous blocknext block →recent activity

Analyzing

Block #86,238,193

26 transactions · 21 stateful · 2026-07-07 17:34:41 UTC

Parallelism

85/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,238,193  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x006ee1d9…5485

0xa6afd3…d132

8 touches
6 conflicts

0xbcdee322…f454

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0xfefb0189…f726

0x34b655…2a6f

6 touches
3 conflicts

0x8eef368f…aa21

0x34b655…2a6f

6 touches
3 conflicts

0xbd9491f7…dd92

0x34b655…2a6f

6 touches
3 conflicts

0xdc57bb0d…6fa9

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

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: Kuru Exchange: Market-WETH/USDC

6 conflicts on slot 0x006ee1d90e…be5485

← previous block·next block →recent activity