← previous blocknext block →recent activity
Analyzing
Block #105,543,236
23 transactions · 22 stateful · 2026-09-17 07:15:36 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,543,236 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w09w110w213w015w117w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3d671ff…a53b
0x34b655…2a6f
8 touches
6 conflicts
0xf496f80c…d5c8
0x34b655…2a6f
8 touches
6 conflicts
0x6771eae2…7014
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x617c91fa…b452
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
6 conflicts on slot 0xb3d671ffb6…6fa53b
Audit this contract →
← previous block·next block →recent activity