← previous blocknext block →recent activity
Analyzing
Block #92,580,368
12 transactions · 12 stateful · 2026-08-02 20:09:46 UTC
Parallelism
33/100
Blocked
58%
Avg conflicts / tx
2.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,580,368 · 12 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x948836ff…59ab
0x34b655…2a6f
6 touches
3 conflicts
0x8ac2787f…f7e1
0x34b655…2a6f
6 touches
3 conflicts
0x672c8097…c166
0x34b655…2a6f
6 touches
3 conflicts
0x460e76af…e1c3
0x34b655…2a6f
6 touches
3 conflicts
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: Perpl
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity