← previous blocknext block →recent activity
Analyzing
Block #92,049,468
14 transactions · 13 stateful · 2026-07-31 23:39:42 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,049,468 · 14 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
4w05w16w07w18w19w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69ee34d1…30f8
0x34b655…2a6f
6 touches
3 conflicts
0xc4d3d66a…d7a8
0x34b655…2a6f
6 touches
3 conflicts
0x892728c9…ce99
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbbee3622…1e03
0x34b655…2a6f
5 touches
3 conflicts
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x7b55198a…b946
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 0x69ee34d107…a730f8
Audit this contract →
← previous block·next block →recent activity