← previous blocknext block →recent activity
Analyzing
Block #92,697,323
12 transactions · 12 stateful · 2026-08-03 05:58:55 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,697,323 · 12 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
3w06w17w08w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd560d5a1…517c
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x1f00a5b3…bf76
0x34b655…2a6f
2 touches
0 conflicts
0x2a53b0a1…a22d
0x34b655…2a6f
2 touches
0 conflicts
0x47d3d221…dbd4
0x34b655…2a6f
2 touches
0 conflicts
0x62611f9e…92c3
0x34b655…2a6f
2 touches
0 conflicts
0x64a785e4…0110
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xd560d5a10f…b2517c
Audit this contract →
← previous block·next block →recent activity