← previous blocknext block →recent activity
Analyzing
Block #96,826,145
15 transactions · 13 stateful · 2026-08-17 16:40:17 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,826,145 · 15 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
1w02w13w04w06w28w313w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06df379f…2653
0x34b655…2a6f
6 touches
3 conflicts
0x2b8d9898…d525
0x34b655…2a6f
6 touches
3 conflicts
0xce6ee9ac…fc82
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2a00a910…f960
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x366c7d57…0ed1
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 0x06df379f10…a22653
Audit this contract →
← previous block·next block →recent activity