← previous blocknext block →recent activity
Analyzing
Block #96,824,740
11 transactions · 10 stateful · 2026-08-17 16:33:13 UTC
Parallelism
73/100
Blocked
40%
Avg conflicts / tx
0.82
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,824,740 · 11 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
1w02w04w05w16w17w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06df379f…2653
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xb733b9da…9c31
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc0a7f33a…341b
0x34b655…2a6f
4 touches
1 conflict
0x352cdf9c…2863
0x34b655…2a6f
4 touches
1 conflict
0x3b56f79b…310f
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 0x06df379f10…a22653
Audit this contract →
← previous block·next block →recent activity