← previous blocknext block →recent activity
Analyzing
Block #105,852,965
20 transactions · 20 stateful · 2026-09-18 09:15:59 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.55
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,852,965 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w18w19w210w311w412w513w014w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0x34959e1a…ce9c
0x34b655…2a6f
10 touches
10 conflicts
0x55192654…91fe
0x34b655…2a6f
10 touches
10 conflicts
0x70f537e8…399b
0x34b655…2a6f
6 touches
3 conflicts
0xd79c9727…1233
0x34b655…2a6f
6 touches
3 conflicts
0xef8f176a…ed6d
0x34b655…2a6f
6 touches
3 conflicts
0x4118bd12…924a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity