← previous blocknext block →recent activity

Analyzing

Block #86,059,006

22 transactions · 18 stateful · 2026-07-06 21:38:36 UTC

Parallelism

86/100

Blocked

39%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,059,006  ·  22 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

0x756913cf…e7bd

0xa6afd3…d132

6 touches
3 conflicts

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x28681974…b88f

0xa6afd3…d132

6 touches
3 conflicts

0xe6e6f436…ddc0

0x34b655…2a6f

4 touches
1 conflict

0xbd9491f7…dd92

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xbfa73fac…6fff

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 0x756913cf06…4ce7bd

← previous block·next block →recent activity