← previous blocknext block →recent activity
Analyzing
Block #106,189,169
36 transactions · 32 stateful · 2026-09-19 13:29:04 UTC
Parallelism
69/100
Blocked
59%
Avg conflicts / tx
1.92
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,189,169 · 36 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w17w211w112w213w315w116w418w519w620w722w724w825w926w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf5419db…6b18
0x34b655…2a6f
12 touches
15 conflicts
0xaa3b4402…74e6
0x34b655…2a6f
12 touches
15 conflicts
0x3af041d1…6f61
0x34b655…2a6f
10 touches
10 conflicts
0x125cf0f0…08e2
0x34b655…2a6f
10 touches
10 conflicts
0xd41f5136…97c6
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x6b267bdf…b173
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0xbf5419db18…726b18
Audit this contract →
← previous block·next block →recent activity