← previous blocknext block →recent activity
Analyzing
Block #106,924,209
38 transactions · 36 stateful · 2026-09-22 03:09:35 UTC
Parallelism
60/100
Blocked
72%
Avg conflicts / tx
2.37
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,924,209 · 38 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w09w210w314w115w216w317w418w519w620w728w131w232w134w236w437w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ec9ff52…e6f7
0x34b655…2a6f
18 touches
36 conflicts
0xfe30e7e5…4a4c
0x34b655…2a6f
16 touches
28 conflicts
0x574628e9…dcc3
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xfc906557…ae7f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0x4ec9ff52ce…67e6f7
Audit this contract →
← previous block·next block →recent activity