← previous blocknext block →recent activity

Analyzing

Block #86,250,953

23 transactions · 20 stateful · 2026-07-07 19:00:02 UTC

Parallelism

87/100

Blocked

30%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,250,953  ·  23 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

0x202c03eb…cf33

0xa6afd3…d132

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xdec5bfea…d17f

0xa6afd3…d132

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x5d5b27f4…e39c

0x754704…b603

4 touches
1 conflict

0xa8669ab5…6af7

0x754704…b603

4 touches
1 conflict

0xaf831072…51d5

0x80f006…d585

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