← previous blocknext block →recent activity
Analyzing
Block #105,857,662
22 transactions · 21 stateful · 2026-09-18 09:39:38 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,857,662 · 22 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
2w06w07w18w114w115w216w317w418w521w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29cd05f5…390c
0x34b655…2a6f
12 touches
15 conflicts
0x1e0d4dd0…1755
0x34b655…2a6f
10 touches
10 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x5a60ac26…4c0b
0x34b655…2a6f
8 touches
6 conflicts
0xba1edffb…323e
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0xa0998a89…1f5a
0x34b655…2a6f
4 touches
1 conflict
0xa13627b9…aad0
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 0x29cd05f5e7…a9390c
Audit this contract →
← previous block·next block →recent activity