← previous blocknext block →recent activity
Analyzing
Block #108,565,985
24 transactions · 23 stateful · 2026-09-27 20:55:39 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,565,985 · 24 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
1w02w13w04w05w16w07w113w214w315w220w021w122w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c4
0x508254…98bd
6 touches
3 conflicts
0xaef80844…aeb9
0x065c9d…c394
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xe1c4d8e8…ffa8
0x508254…98bd
6 touches
3 conflicts
0x467e524d…3987
0x508254…98bd
6 touches
3 conflicts
0x3347d4cb…656d
0xd32edf…ff58
5 touches
3 conflicts
0xd98b3c10…67b8
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: 0x508254c8…4a98bd
3 conflicts on slot 0x3a663e9a3a…2fa9c4
Audit this contract →
← previous block·next block →recent activity