← previous blocknext block →recent activity
Analyzing
Block #105,932,816
22 transactions · 21 stateful · 2026-09-18 15:58:46 UTC
Parallelism
64/100
Blocked
52%
Avg conflicts / tx
1.32
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,932,816 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w19w210w311w412w513w614w721w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14e6dc74…6e3b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0xd7509533…7142
0x34b655…2a6f
8 touches
6 conflicts
0xd4fb3441…c092
0x34b655…2a6f
8 touches
6 conflicts
0x3a429191…9cda
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xbeedaa05…9eda
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
10 conflicts on slot 0x14e6dc7463…3c6e3b
Audit this contract →
← previous block·next block →recent activity