← previous blocknext block →recent activity
Analyzing
Block #108,960,680
15 transactions · 14 stateful · 2026-09-29 06:06:39 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,960,680 · 15 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
3w04w16w07w18w29w310w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x233baba5…8702
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xef99996b…44ab
0x34b655…2a6f
6 touches
3 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
6 touches
3 conflicts
0x1af9143d…be5c
0x851145…3f07
4 touches
1 conflict
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x2b60abad…2240
0x34b655…2a6f
4 touches
1 conflict
0x9375a764…dca1
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
3 conflicts on slot 0x233baba574…5f8702
Audit this contract →
← previous block·next block →recent activity