← previous blocknext block →recent activity
Analyzing
Block #93,372,619
24 transactions · 20 stateful · 2026-08-05 14:37:11 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,372,619 · 24 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
5w06w19w010w111w212w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x07b83266…e5ee
0xd32edf…ff58
5 touches
3 conflicts
0x28f324ed…9db7
0x34b655…2a6f
4 touches
1 conflict
0xd244f609…4316
0x34b655…2a6f
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
2 touches
0 conflicts
0x11b69a7e…334e
0x01bff4…1071
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity