← previous blocknext block →recent activity
Analyzing
Block #107,848,723
38 transactions · 36 stateful · 2026-09-25 08:45:27 UTC
Parallelism
84/100
Blocked
61%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,848,723 · 38 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
2w03w14w05w16w07w18w29w310w011w112w013w115w216w319w322w432w235w236w337w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fef5199…111a
0x34b655…2a6f
10 touches
10 conflicts
0xfd4e632c…e14c
0x34b655…2a6f
10 touches
10 conflicts
0xba522812…1f1f
0x34b655…2a6f
10 touches
10 conflicts
0x94b6efbd…d34a
0x34b655…2a6f
10 touches
10 conflicts
0xe430885b…9252
0xd32edf…ff58
9 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0x7fef51998c…6d111a
Audit this contract →
← previous block·next block →recent activity