← previous blocknext block →recent activity
Analyzing
Block #92,650,136
14 transactions · 12 stateful · 2026-08-03 02:00:42 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,650,136 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w16w27w29w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0a5e3b4…2700
0x34b655…2a6f
8 touches
6 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x32e2bb09…8b3a
0x34b655…2a6f
6 touches
3 conflicts
0x65122952…a5ac
0x34b655…2a6f
4 touches
1 conflict
0x1bb56de3…732e
0x34b655…2a6f
4 touches
1 conflict
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0xc0a5e3b4e4…522700
Audit this contract →
← previous block·next block →recent activity