← previous blocknext block →recent activity
Analyzing
Block #106,199,443
27 transactions · 26 stateful · 2026-09-19 14:20:46 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.26
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,199,443 · 27 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
1w03w04w15w26w37w48w59w113w623w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98568c43…ff4e
0x34b655…2a6f
14 touches
21 conflicts
0x80097eeb…0247
0x34b655…2a6f
12 touches
15 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x79254875…30ac
0x34b655…2a6f
6 touches
3 conflicts
0x7cf3eb0f…06c5
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x07610b8e…6093
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 0x98568c43d7…70ff4e
Audit this contract →
← previous block·next block →recent activity