← previous blocknext block →recent activity

Analyzing

Block #86,852,309

22 transactions · 21 stateful · 2026-07-10 14:00:27 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,852,309  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0xa6afd3…d132

10 touches
10 conflicts

0x17c44db3…8888

0xa6afd3…d132

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x4f4bdabd…ffba

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xbcdee322…f454

0xa6afd3…d132

6 touches
3 conflicts

0x8cc1393f…07fb

0x34b655…2a6f

6 touches
3 conflicts

0x40970e69…da50

0x69df8a…6292

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity