← previous blocknext block →recent activity
Analyzing
Block #106,955,357
33 transactions · 30 stateful · 2026-09-22 05:46:22 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,955,357 · 33 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
1w03w04w15w26w37w08w19w211w414w518w519w624w127w729w830w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3611ffd1…1232
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x858e40c0…7e30
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x51aa664e…d3b8
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x6d5d1fb5…86a7
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 0x3611ffd156…191232
Audit this contract →
← previous block·next block →recent activity