← previous blocknext block →recent activity
Analyzing
Block #109,161,617
18 transactions · 15 stateful · 2026-09-29 23:00:50 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,161,617 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w112w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
12 touches
15 conflicts
0x7dd96c96…7335
0x34b655…2a6f
12 touches
15 conflicts
0x98235cbb…7490
0x34b655…2a6f
8 touches
6 conflicts
0xac38cd2f…5c85
0x34b655…2a6f
6 touches
3 conflicts
0x024b482b…16b0
0x34b655…2a6f
6 touches
3 conflicts
0xb09246c2…32f5
0x34b655…2a6f
5 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
15 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity