← previous blocknext block →recent activity
Analyzing
Block #96,560,943
12 transactions · 10 stateful · 2026-08-16 18:26:24 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,560,943 · 12 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
4w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6100f5dd…6a7f
0x34b655…2a6f
6 touches
3 conflicts
0xff9e45bf…99a0
0x34b655…2a6f
6 touches
3 conflicts
0x7badba13…1a09
0x34b655…2a6f
6 touches
3 conflicts
0x6246af59…213f
0x34b655…2a6f
4 touches
1 conflict
0x7ce5b49a…237c
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
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 0x6100f5dd6f…7a6a7f
Audit this contract →
← previous block·next block →recent activity