← previous blocknext block →recent activity

Analyzing

Block #91,248,674

18 transactions · 17 stateful · 2026-07-29 04:28:58 UTC

Parallelism

83/100

Blocked

41%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #91,248,674  ·  18 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

0x529e53cf…38e4

0xa6afd3…d132

4 touches
1 conflict

0xdedb36e7…3585

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x250c3574…21db

0x851145…3f07

4 touches
1 conflict

0xf8ceaa24…6e8e

0x851145…3f07

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x3230413b…bc7f

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

1 conflict on slot 0x529e53cf07…5438e4

← previous block·next block →recent activity