← previous blocknext block →recent activity
Analyzing
Block #106,935,088
50 transactions · 40 stateful · 2026-09-22 04:04:20 UTC
Parallelism
84/100
Blocked
68%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,935,088 · 50 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
1w05w16w07w18w29w010w111w217w319w121w226w432w540w441w142w645w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd906863d…b52b
0x34b655…2a6f
14 touches
21 conflicts
0x206f4379…e08a
0x34b655…2a6f
12 touches
15 conflicts
0x173787cc…2319
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x469dac8d…3411
0x34b655…2a6f
8 touches
6 conflicts
0x7fc8f46e…0f75
0x34b655…2a6f
8 touches
6 conflicts
0xc8c615d4…5da3
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
21 conflicts on slot 0xd906863d12…42b52b
Audit this contract →
← previous block·next block →recent activity