← previous blocknext block →recent activity
Analyzing
Block #109,177,136
29 transactions · 21 stateful · 2026-09-30 00:18:55 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,177,136 · 29 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
3w04w17w015w016w117w218w319w420w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91f9f021…0820
0x34b655…2a6f
10 touches
10 conflicts
0xdf6bf6a6…42fa
0x34b655…2a6f
10 touches
10 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
8 touches
6 conflicts
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x68f7aaba…88df
0x34b655…2a6f
4 touches
1 conflict
0x9a8482cc…8bee
0x34b655…2a6f
4 touches
1 conflict
0xdacb24f7…56ce
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
10 conflicts on slot 0x91f9f0213b…9c0820
Audit this contract →
← previous block·next block →recent activity