← previous blocknext block →recent activity
Analyzing
Block #108,672,030
17 transactions · 17 stateful · 2026-09-28 05:49:37 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,672,030 · 17 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
5w06w18w110w211w312w413w514w216w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d7f568a…5810
0x34b655…2a6f
10 touches
10 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
6 touches
3 conflicts
0xf15273a1…2c52
0x34b655…2a6f
6 touches
3 conflicts
0xa03c2a35…52e6
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
0x34b655…2a6f
4 touches
1 conflict
0x23769ebc…c8ed
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0x8d7f568a9a…bd5810
Audit this contract →
← previous block·next block →recent activity