← previous blocknext block →recent activity

Analyzing

Block #88,137,922

16 transactions · 16 stateful · 2026-07-16 13:18:30 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,137,922  ·  16 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

0xa4f80979…4d71

0x065c9d…c394

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x59dccbd8…2bf6

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x799aea28…88dc

0x851145…3f07

4 touches
1 conflict

0x8882fafc…f2eb

0x065c9d…c394

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x0733be30…112f

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-MON/USDC

3 conflicts on slot 0xa4f8097941…fd4d71

← previous block·next block →recent activity