← previous blocknext block →recent activity
Analyzing
Block #108,010,091
11 transactions · 10 stateful · 2026-09-25 22:17:44 UTC
Parallelism
55/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,010,091 · 11 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
1w02w03w04w15w26w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x179b31b3…6dd2
0x34b655…2a6f
4 touches
1 conflict
0x20492d53…80f9
0x34b655…2a6f
4 touches
1 conflict
0x471711ec…240a
0x34b655…2a6f
4 touches
1 conflict
0xf92a8532…da78
0x34b655…2a6f
4 touches
1 conflict
0x024b482b…16b0
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
6 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity