← previous blocknext block →recent activity
Analyzing
Block #106,235,470
36 transactions · 33 stateful · 2026-09-19 17:22:12 UTC
Parallelism
69/100
Blocked
64%
Avg conflicts / tx
1.69
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,235,470 · 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
1w02w13w04w05w26w37w48w510w111w618w120w721w122w123w725w826w927w1032w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf00e711b…c539
0x34b655…2a6f
16 touches
28 conflicts
0x065566a3…cf1b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x73b87bc2…457a
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
28 conflicts on slot 0xf00e711b37…00c539
Audit this contract →
← previous block·next block →recent activity