← previous blocknext block →recent activity

Analyzing

Block #86,328,840

24 transactions · 20 stateful · 2026-07-08 03:40:00 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,328,840  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xca0f0668…caf3

0xa6afd3…d132

8 touches
6 conflicts

0xb68e226d…c054

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x96dd83e6…a507

0x34b655…2a6f

4 touches
1 conflict

0x71c06d29…47bd

0xa6afd3…d132

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x22e0cc1d…ad0d

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

6 conflicts on slot 0xca0f066838…0ccaf3

← previous block·next block →recent activity