← previous blocknext block →recent activity
Analyzing
Block #106,253,602
20 transactions · 19 stateful · 2026-09-19 18:53:27 UTC
Parallelism
70/100
Blocked
32%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,253,602 · 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
1w08w09w115w216w317w418w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfef9b8c0…3db5
0x34b655…2a6f
12 touches
15 conflicts
0xdb7ffa78…ab30
0x34b655…2a6f
10 touches
10 conflicts
0x38c6ff01…689f
0x34b655…2a6f
6 touches
3 conflicts
0xe43b345e…a4e3
0x34b655…2a6f
6 touches
3 conflicts
0xecd87a39…d9c5
0x34b655…2a6f
6 touches
3 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
6 touches
3 conflicts
0x5906754f…b584
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
15 conflicts on slot 0xfef9b8c0f8…633db5
Audit this contract →
← previous block·next block →recent activity