← previous blocknext block →recent activity
Analyzing
Block #96,600,259
24 transactions · 22 stateful · 2026-08-16 21:44:10 UTC
Parallelism
88/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,600,259 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w18w29w212w215w016w117w118w019w120w221w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x1e10796e…6213
0x34b655…2a6f
4 touches
1 conflict
0x3226e3fe…f799
0x34b655…2a6f
4 touches
1 conflict
0x427c9fc4…5cee
0x34b655…2a6f
4 touches
1 conflict
0x4acc6dca…a868
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 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity