← previous blocknext block →recent activity

Analyzing

Block #86,619,053

29 transactions · 21 stateful · 2026-07-09 12:01:01 UTC

Parallelism

90/100

Blocked

29%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,619,053  ·  29 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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xb43dc900…22f2

0xa6afd3…d132

6 touches
3 conflicts

0x9da6e429…074d

0xa6afd3…d132

6 touches
3 conflicts

0x8eb0ac6b…a73a

0x34b655…2a6f

4 touches
1 conflict

0x94367ac0…5d5d

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab0

0x34b655…2a6f

4 touches
1 conflict

0xa4e9800f…4ab1

0x34b655…2a6f

4 touches
1 conflict

0xab207661…7e14

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 0x0000000000…00003d

← previous block·next block →recent activity