← previous blocknext block →recent activity
Analyzing
Block #107,640,601
29 transactions · 25 stateful · 2026-09-24 15:16:29 UTC
Parallelism
86/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,640,601 · 29 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
1w02w03w15w06w17w28w39w011w115w016w117w018w120w122w023w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1a6bdef5…144d
0x34b655…2a6f
4 touches
1 conflict
0x23a62f18…bade
0x34b655…2a6f
4 touches
1 conflict
0x3dd291e1…f3ee
0x34b655…2a6f
4 touches
1 conflict
0x4a45b318…9716
0x34b655…2a6f
4 touches
1 conflict
0x6780726b…4864
0x34b655…2a6f
4 touches
1 conflict
0x7499cc33…a306
0x34b655…2a6f
4 touches
1 conflict
0x74cdc294…26a8
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
3 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity