← previous blocknext block →recent activity
Analyzing
Block #105,851,717
21 transactions · 20 stateful · 2026-09-18 09:09:42 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,851,717 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w112w214w315w416w517w618w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdcd58096…bb7a
0x34b655…2a6f
14 touches
21 conflicts
0xac389ba9…8b45
0x34b655…2a6f
14 touches
21 conflicts
0xa2ff4baa…16f4
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
6 touches
3 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x2185f870…11f6
0x34b655…2a6f
4 touches
1 conflict
0x41f700a1…b4f8
0x34b655…2a6f
4 touches
1 conflict
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 0xdcd5809626…a9bb7a
Audit this contract →
← previous block·next block →recent activity