← previous blocknext block →recent activity
Analyzing
Block #106,199,768
23 transactions · 19 stateful · 2026-09-19 14:22:25 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,199,768 · 23 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
1w02w03w14w06w210w312w313w415w416w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59ec0dd4…543c
0x34b655…2a6f
14 touches
21 conflicts
0x3ec53e25…569f
0x34b655…2a6f
12 touches
15 conflicts
0x5717771c…45ed
0x34b655…2a6f
12 touches
15 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbeedaa05…9eda
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 0x59ec0dd4a7…2d543c
Audit this contract →
← previous block·next block →recent activity