← previous blocknext block →recent activity
Analyzing
Block #106,215,922
24 transactions · 24 stateful · 2026-09-19 15:43:46 UTC
Parallelism
67/100
Blocked
46%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,215,922 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w29w010w112w013w214w315w416w517w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3865a46d…09f8
0x34b655…2a6f
14 touches
21 conflicts
0xb7af7ea3…7d7d
0x34b655…2a6f
14 touches
21 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
6 touches
3 conflicts
0xab981df1…2941
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xecf22f58…5939
0x34b655…2a6f
6 touches
3 conflicts
0xfbabb02d…af07
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
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
21 conflicts on slot 0x3865a46d85…8e09f8
Audit this contract →
← previous block·next block →recent activity