← previous blocknext block →recent activity

Analyzing

Block #86,661,249

27 transactions · 20 stateful · 2026-07-09 16:44:10 UTC

Parallelism

89/100

Blocked

30%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,661,249  ·  27 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x52e69143…95ad

0x065c9d…c394

6 touches
3 conflicts

0xce827910…ff22

0x065c9d…c394

6 touches
3 conflicts

0xc0eb79d1…29a4

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x1941b441…5889

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 0x0000000000…00003d

← previous block·next block →recent activity