← previous blocknext block →recent activity
Analyzing
Block #109,161,774
31 transactions · 27 stateful · 2026-09-29 23:01:37 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,161,774 · 31 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
3w04w08w19w110w211w212w314w417w123w329w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5ac4b35…7e68
0x34b655…2a6f
8 touches
6 conflicts
0x1418835a…7906
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
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
6 conflicts on slot 0xc5ac4b35f0…c57e68
Audit this contract →
← previous block·next block →recent activity