← previous blocknext block →recent activity
Analyzing
Block #92,767,582
13 transactions · 13 stateful · 2026-08-03 11:52:35 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,767,582 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w38w410w511w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6c175be…c05e
0x34b655…2a6f
6 touches
3 conflicts
0x1d674032…2e0a
0x34b655…2a6f
6 touches
3 conflicts
0x9365e097…ff56
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc890aece…c5b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd0bb8d8a…16a9
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: Perpl
3 conflicts on slot 0xd6c175bee6…f5c05e
Audit this contract →
← previous block·next block →recent activity