← previous blocknext block →recent activity

Analyzing

Block #88,341,423

24 transactions · 22 stateful · 2026-07-17 12:00:06 UTC

Parallelism

88/100

Blocked

27%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #88,341,423  ·  24 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

0x160f117d…8e90

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xfebaf6fc…61b5

0x34b655…2a6f

4 touches
1 conflict

0xc4c059d8…185d

0x34b655…2a6f

4 touches
1 conflict

0xd06d821c…e5d0

0x34b655…2a6f

4 touches
1 conflict

0xf4beb400…c00f

0x34b655…2a6f

4 touches
1 conflict

0xb33ff823…1188

0x065c9d…c394

4 touches
1 conflict

0x00ddbbf2…4588

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 0x160f117d43…518e90

← previous block·next block →recent activity