← previous blocknext block →recent activity
Analyzing
Block #106,215,575
25 transactions · 24 stateful · 2026-09-19 15:42:01 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
2.04
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,215,575 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w07w111w314w415w516w617w618w719w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecf22f58…5939
0x34b655…2a6f
14 touches
21 conflicts
0x638cd0f2…cb93
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
10 touches
10 conflicts
0x22f5401b…855c
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x2d84ae4b…161b
0x34b655…2a6f
8 touches
6 conflicts
0xecd87a39…d9c5
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
21 conflicts on slot 0xecf22f58ca…2c5939
Audit this contract →
← previous block·next block →recent activity