← previous blocknext block →recent activity
Analyzing
Block #106,956,231
26 transactions · 22 stateful · 2026-09-22 05:50:46 UTC
Parallelism
73/100
Blocked
32%
Avg conflicts / tx
0.85
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,956,231 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w09w110w211w312w419w520w624w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
12 touches
15 conflicts
0x155e52ca…fac7
0x34b655…2a6f
12 touches
15 conflicts
0xf1ad394c…ae23
0x34b655…2a6f
10 touches
10 conflicts
0xcf745c27…6dbc
0x34b655…2a6f
8 touches
6 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
6 touches
3 conflicts
0x26799298…9ff2
0x34b655…2a6f
6 touches
3 conflicts
0x858e40c0…7e30
0x34b655…2a6f
4 touches
1 conflict
0xb3d828cf…a9b8
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
15 conflicts on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity