← previous blocknext block →recent activity
Analyzing
Block #106,917,907
19 transactions · 19 stateful · 2026-09-22 02:37:52 UTC
Parallelism
58/100
Blocked
37%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,917,907 · 19 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
6w07w18w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x17d75238…7d7c
0x34b655…2a6f
16 touches
28 conflicts
0xe4af4c87…9964
0x34b655…2a6f
16 touches
28 conflicts
0x3093e806…bde2
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x518221db…65f7
0x34b655…2a6f
2 touches
0 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
2 touches
0 conflicts
0x9daee8ff…6f86
0x34b655…2a6f
2 touches
0 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 0xccebf5c5cb…c88758
Audit this contract →
← previous block·next block →recent activity