← previous blocknext block →recent activity

Analyzing

Block #86,690,013

22 transactions · 21 stateful · 2026-07-09 19:56:10 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,690,013  ·  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

0xfc578b53…9b1f

0xa6afd3…d132

4 touches
1 conflict

0x342fbbca…d443

0x40c49f…2af0

4 touches
1 conflict

0xffa7d0a4…b10a

0x40c49f…2af0

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x427d1120…4eb1

0x34b655…2a6f

4 touches
1 conflict

0x6f900be0…cd6e

0x34b655…2a6f

4 touches
1 conflict

0x74888025…a5b8

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

1 conflict on slot 0xfc578b53da…c79b1f

← previous block·next block →recent activity