← previous blocknext block →recent activity
Analyzing
Block #105,575,581
20 transactions · 18 stateful · 2026-09-17 09:58:24 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.85
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,575,581 · 20 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
1w02w03w16w07w18w19w210w011w112w213w315w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9aaeabb1…4646
0x34b655…2a6f
8 touches
6 conflicts
0xcd93b2d2…30e6
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
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 0x9aaeabb113…364646
Audit this contract →
← previous block·next block →recent activity