← previous blocknext block →recent activity
Analyzing
Block #96,665,469
16 transactions · 12 stateful · 2026-08-17 03:12:08 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,665,469 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w26w37w19w214w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe6a366…8ca1
0x34b655…2a6f
10 touches
10 conflicts
0x03aa8b26…118a
0x34b655…2a6f
6 touches
3 conflicts
0x2840c278…bbc7
0x34b655…2a6f
6 touches
3 conflicts
0x2de9863d…96dc
0x34b655…2a6f
4 touches
1 conflict
0x59d06fe7…5d00
0x34b655…2a6f
4 touches
1 conflict
0x6e389ca9…17e8
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
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
10 conflicts on slot 0xfbe6a36638…508ca1
Audit this contract →
← previous block·next block →recent activity