← previous blocknext block →recent activity
Analyzing
Block #109,228,958
13 transactions · 13 stateful · 2026-09-30 04:39:46 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #109,228,958 · 13 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
1w03w04w15w210w011w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d9ef283…ddd1
0x34b655…2a6f
8 touches
6 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
6 touches
3 conflicts
0xeb1b4ae8…64bd
0x37db7f…ec7b
6 touches
3 conflicts
0xe2d50773…c39e
0x34b655…2a6f
6 touches
3 conflicts
0x469854ac…edcd
0x34b655…2a6f
6 touches
3 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x238d0a65…428b
0x37db7f…ec7b
6 touches
3 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
6 conflicts on slot 0x7d9ef2836a…01ddd1
Audit this contract →
← previous block·next block →recent activity