← previous blocknext block →recent activity

Analyzing

Block #86,944,242

24 transactions · 21 stateful · 2026-07-11 00:15:05 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,944,242  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd35bb5ac…3586

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x94ba9c4a…41d8

0x34b655…2a6f

6 touches
3 conflicts

0x7d42dc8b…fdb6

0x2a68ba…90c5

4 touches
1 conflict

0x24d58d14…f7a5

0x34b655…2a6f

4 touches
1 conflict

0x3347cbe5…846c

0x34b655…2a6f

4 touches
1 conflict

0x5d7d3d99…cd99

0x34b655…2a6f

4 touches
1 conflict

0x5f251b96…6054

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

6 conflicts on slot 0xd35bb5ac3f…003586

← previous block·next block →recent activity