← previous blocknext block →recent activity

Analyzing

Block #86,828,014

20 transactions · 17 stateful · 2026-07-10 11:18:06 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,828,014  ·  20 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

0x17c44db3…8888

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x236b16bf…ea47

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3e690221…c7e3

0x34b655…2a6f

4 touches
1 conflict

0x3e690221…c7e4

0x34b655…2a6f

4 touches
1 conflict

0x4d7e366b…7690

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 0x17c44db3e4…ef8888

← previous block·next block →recent activity