← previous blocknext block →recent activity
Analyzing
Block #96,640,403
29 transactions · 26 stateful · 2026-08-17 01:06:04 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,640,403 · 29 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
2w04w07w08w19w210w011w114w019w020w121w022w223w024w325w126w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7f67d8a…1412
0x34b655…2a6f
8 touches
6 conflicts
0x05896939…9f49
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea1b8c07…b969
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xb5c7c6aa…fdba
0x34b655…2a6f
4 touches
1 conflict
0xbe7cdf02…b1e4
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 0xf7f67d8a8f…171412
Audit this contract →
← previous block·next block →recent activity