← previous blocknext block →recent activity
Analyzing
Block #106,467,316
18 transactions · 17 stateful · 2026-09-20 12:49:01 UTC
Parallelism
44/100
Blocked
53%
Avg conflicts / tx
2.11
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,467,316 · 18 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w310w411w512w613w715w816w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe890a5b…ac60
0x34b655…2a6f
16 touches
28 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xa8c7d195…3077
0x34b655…2a6f
8 touches
6 conflicts
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
6 touches
3 conflicts
0x46483cb1…e7ca
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 0xfe890a5b12…49ac60
Audit this contract →
← previous block·next block →recent activity