← previous blocknext block →recent activity
Analyzing
Block #105,367,328
15 transactions · 14 stateful · 2026-09-16 16:30:15 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,367,328 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w110w112w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xc00c1308…6485
0x34b655…2a6f
6 touches
3 conflicts
0xf2de8909…1eed
0x34b655…2a6f
4 touches
1 conflict
0x8692136a…16fc
0x34b655…2a6f
4 touches
1 conflict
0x99c8b719…5f38
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xc7d734c2…b3f8
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity