← previous blocknext block →recent activity

Analyzing

Block #91,780,068

14 transactions · 12 stateful · 2026-07-31 01:04:30 UTC

Parallelism

86/100

Blocked

17%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #91,780,068  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x28c714d9…9438

0xa6afd3…d132

4 touches
1 conflict

0x04c3f565…dc64

0x34b655…2a6f

4 touches
1 conflict

0x153d1e25…10ea

0x34b655…2a6f

4 touches
1 conflict

0x455a8076…be99

0x34b655…2a6f

4 touches
1 conflict

0x4f1ad4b4…e00a

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b77

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x9b6c3273…9421

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 0x28c714d9f2…089438

← previous block·next block →recent activity