← previous blocknext block →recent activity
Analyzing
Block #106,537,825
18 transactions · 18 stateful · 2026-09-20 18:43:53 UTC
Parallelism
78/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,537,825 · 18 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
1w02w13w04w17w19w011w112w213w214w315w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69411fb3…e36d
0x34b655…2a6f
8 touches
6 conflicts
0xf6a9ddc6…4bc4
0x34b655…2a6f
8 touches
6 conflicts
0xb9b077a8…e029
0x34b655…2a6f
8 touches
6 conflicts
0x46a5ec6c…f318
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x3b6e959d…158f
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
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 0x69411fb3ba…bce36d
Audit this contract →
← previous block·next block →recent activity