← previous blocknext block →recent activity

Analyzing

Block #86,850,954

23 transactions · 16 stateful · 2026-07-10 13:51:23 UTC

Parallelism

78/100

Blocked

56%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,850,954  ·  23 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

0xbcdee322…f454

0xa6afd3…d132

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf81d0d0f…cf78

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x50c730d7…8540

0x34b655…2a6f

4 touches
1 conflict

0x78d79dcd…a930

0x34b655…2a6f

4 touches
1 conflict

0x78d79dcd…a931

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 0xbcdee3220a…7cf454

← previous block·next block →recent activity