← previous blocknext block →recent activity

Analyzing

Block #91,769,924

22 transactions · 19 stateful · 2026-07-31 00:13:28 UTC

Parallelism

82/100

Blocked

37%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #91,769,924  ·  22 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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x103be197…826c

0xa6afd3…d132

6 touches
3 conflicts

0x97e435dc…cfe6

0xa6afd3…d132

4 touches
2 conflicts

0x70b7b52e…7743

0x34b655…2a6f

4 touches
1 conflict

0x70b7b52e…7744

0x34b655…2a6f

4 touches
1 conflict

0x7118f456…6083

0x34b655…2a6f

4 touches
1 conflict

0x7c09c53e…64b4

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