← previous blocknext block →recent activity
Analyzing
Block #109,137,686
20 transactions · 16 stateful · 2026-09-29 21:00:00 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,137,686 · 20 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
1w02w17w08w19w211w315w316w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x742e5c25…a6b2
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x5b4c80c8…c242
0x34b655…2a6f
6 touches
3 conflicts
0x67318be2…6e11
0x34b655…2a6f
6 touches
3 conflicts
0x7499cc33…a306
0x34b655…2a6f
6 touches
3 conflicts
0x7d9ef283…ddd1
0x34b655…2a6f
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
10 conflicts on slot 0x742e5c25e5…73a6b2
Audit this contract →
← previous block·next block →recent activity