← previous blocknext block →recent activity
Analyzing
Block #108,532,018
37 transactions · 28 stateful · 2026-09-27 18:04:27 UTC
Parallelism
86/100
Blocked
32%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,532,018 · 37 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w18w211w112w214w315w324w325w033w335w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b780b26…f5ff
0x34b655…2a6f
10 touches
10 conflicts
0x60e5418d…038a
0x34b655…2a6f
8 touches
6 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
8 touches
6 conflicts
0xc9a59d29…f159
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
6 touches
3 conflicts
0xa7199234…a277
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
10 conflicts on slot 0x8b780b2668…85f5ff
Audit this contract →
← previous block·next block →recent activity