← previous blocknext block →recent activity
Analyzing
Block #96,654,633
18 transactions · 16 stateful · 2026-08-17 02:17:38 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.72
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,654,633 · 18 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
1w02w04w15w27w18w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d4376db…414c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
6 touches
3 conflicts
0x602ed980…5e88
0x34b655…2a6f
4 touches
1 conflict
0x602ed980…5e89
0x34b655…2a6f
4 touches
1 conflict
0x619f6301…19b3
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 0x6d4376dbac…c2414c
Audit this contract →
← previous block·next block →recent activity