← previous blocknext block →recent activity
Analyzing
Block #106,917,162
30 transactions · 28 stateful · 2026-09-22 02:34:07 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
1.37
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,917,162 · 30 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
1w02w13w25w06w18w09w113w314w420w222w523w624w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5113c90…6d10
0x34b655…2a6f
16 touches
28 conflicts
0x94e7f277…471b
0x34b655…2a6f
12 touches
15 conflicts
0xf1bbd371…e541
0x34b655…2a6f
10 touches
10 conflicts
0x2130a548…c1de
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x26be85b6…cb00
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
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 0xe5113c908a…bc6d10
Audit this contract →
← previous block·next block →recent activity