← previous blocknext block →recent activity

Analyzing

Block #91,417,658

28 transactions · 18 stateful · 2026-07-29 18:40:29 UTC

Parallelism

89/100

Blocked

39%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,417,658  ·  28 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

0x439cfb2c…7b9e

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x103be197…826c

0xa6afd3…d132

6 touches
3 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

4 touches
1 conflict

0xb05cd4f5…73d0

0x2b46c0…1669

4 touches
1 conflict

0xdb067026…9eb8

0x2b46c0…1669

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

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 0x439cfb2c22…b27b9e

← previous block·next block →recent activity