← previous blocknext block →recent activity
Analyzing
Block #93,565,899
11 transactions · 11 stateful · 2026-08-06 06:48:51 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,565,899 · 11 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
3w04w16w27w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac28c0f0…79c2
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x98212952…9ba6
0x34b655…2a6f
6 touches
3 conflicts
0x46ee3c65…4ab8
0x34b655…2a6f
4 touches
1 conflict
0x6561b826…f343
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b77
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
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 0xac28c0f0b1…8679c2
Audit this contract →
← previous block·next block →recent activity