← previous blocknext block →recent activity
Analyzing
Block #106,930,650
22 transactions · 21 stateful · 2026-09-22 03:42:00 UTC
Parallelism
64/100
Blocked
43%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,930,650 · 22 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
5w06w07w18w29w310w411w512w613w719w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70986451…c6bd
0x34b655…2a6f
10 touches
10 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
10 touches
10 conflicts
0x98783aa8…b36c
0x34b655…2a6f
8 touches
6 conflicts
0xccebf5c5…8758
0x34b655…2a6f
8 touches
6 conflicts
0x251ee419…4404
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x85c5ea16…1194
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
10 conflicts on slot 0x7098645134…3ac6bd
Audit this contract →
← previous block·next block →recent activity