← previous blocknext block →recent activity
Analyzing
Block #105,608,055
18 transactions · 16 stateful · 2026-09-17 12:41:52 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,608,055 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w112w213w315w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd20e6a3…91e5
0x34b655…2a6f
8 touches
6 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
6 touches
3 conflicts
0xdcebb2b8…5f18
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x711e4ba1…40ee
0x34b655…2a6f
4 touches
1 conflict
0x8f84702c…c5f9
0x34b655…2a6f
4 touches
1 conflict
0x904e2bfb…1544
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 0xdd20e6a389…8991e5
Audit this contract →
← previous block·next block →recent activity