← previous blocknext block →recent activity

Analyzing

Block #86,612,475

20 transactions · 16 stateful · 2026-07-09 11:17:05 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,612,475  ·  20 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

0x9da6e429…074d

0xa6afd3…d132

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xb43dc900…22f2

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xfb4cb196…8c4a

0x34b655…2a6f

6 touches
3 conflicts

0x875c3459…2878

0x34b655…2a6f

4 touches
1 conflict

0x875c3459…2879

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

3 conflicts on slot 0x9da6e42935…3b074d

← previous block·next block →recent activity