← previous blocknext block →recent activity
Analyzing
Block #96,522,676
13 transactions · 9 stateful · 2026-08-16 15:13:57 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,522,676 · 13 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
1w02w13w27w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86c98782…f3b7
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x6c3179e8…bfe9
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
2 touches
0 conflicts
0x27852ce6…885c
0x34b655…2a6f
2 touches
0 conflicts
0x2e7a0c1d…caaf
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
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
3 conflicts on slot 0x86c98782f1…e7f3b7
Audit this contract →
← previous block·next block →recent activity