← previous blocknext block →recent activity
Analyzing
Block #109,137,714
23 transactions · 21 stateful · 2026-09-29 21:00:09 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,137,714 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w310w411w520w021w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742e5c25…a6b2
0x34b655…2a6f
14 touches
21 conflicts
0x3243e72f…1f6d
0x34b655…2a6f
12 touches
15 conflicts
0x487cc6ea…24a5
0x34b655…2a6f
12 touches
15 conflicts
0x5969523e…5191
0x34b655…2a6f
12 touches
15 conflicts
0x5b4c80c8…c242
0x34b655…2a6f
12 touches
15 conflicts
0x67318be2…6e11
0x34b655…2a6f
12 touches
15 conflicts
0x7499cc33…a306
0x34b655…2a6f
12 touches
15 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
12 touches
15 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
21 conflicts on slot 0x742e5c25e5…73a6b2
Audit this contract →
← previous block·next block →recent activity