← previous blocknext block →recent activity
Analyzing
Block #106,565,449
20 transactions · 18 stateful · 2026-09-20 21:02:53 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,565,449 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w110w212w314w315w416w518w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x663784e7…acb8
0x34b655…2a6f
10 touches
10 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
8 touches
6 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xf1e3b327…e168
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x4089d428…b018
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0x663784e73e…28acb8
Audit this contract →
← previous block·next block →recent activity