← previous blocknext block →recent activity
Analyzing
Block #106,428,304
25 transactions · 24 stateful · 2026-09-20 09:32:37 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,428,304 · 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
5w06w17w210w011w114w115w216w317w418w519w620w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fd19f68…126f
0x34b655…2a6f
12 touches
15 conflicts
0x8d664414…3344
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0xa7b29d23…096f
0x34b655…2a6f
6 touches
3 conflicts
0xb6fcbbb7…2b31
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
15 conflicts on slot 0x7fd19f68a5…e9126f
Audit this contract →
← previous block·next block →recent activity