← previous blocknext block →recent activity

Analyzing

Block #86,911,504

23 transactions · 23 stateful · 2026-07-10 20:36:22 UTC

Parallelism

87/100

Blocked

26%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,911,504  ·  23 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

0xe06bbb2e…9416

0x34b655…2a6f

6 touches
3 conflicts

0xd35bb5ac…3586

0x065c9d…c394

6 touches
3 conflicts

0xe5a6ab32…42a0

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7e231c33…6567

0x065c9d…c394

5 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x9eaf42da…f13b

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