← previous blocknext block →recent activity
Analyzing
Block #106,930,847
33 transactions · 32 stateful · 2026-09-22 03:43:00 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,930,847 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w09w110w111w212w313w214w115w216w317w418w522w324w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53ca1284…cb2c
0x34b655…2a6f
12 touches
15 conflicts
0xa8632652…b6e0
0x34b655…2a6f
12 touches
15 conflicts
0xf782ee27…41cd
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
10 touches
10 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x53ca128412…cacb2c
Audit this contract →
← previous block·next block →recent activity