← previous blocknext block →recent activity
Analyzing
Block #96,352,191
11 transactions · 10 stateful · 2026-08-16 00:56:11 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,352,191 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0xdec6a8f8…be18
0x34b655…2a6f
6 touches
3 conflicts
0x17935a8f…a796
0x34b655…2a6f
4 touches
1 conflict
0x17b720f5…ad7a
0x34b655…2a6f
4 touches
1 conflict
0x18cf36a6…a3a3
0x34b655…2a6f
4 touches
1 conflict
0x202ded7c…aca4
0x34b655…2a6f
4 touches
1 conflict
0x22bdb66a…cec9
0x34b655…2a6f
4 touches
1 conflict
0x3c7c65d0…0b52
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity