← previous blocknext block →recent activity
Analyzing
Block #109,176,179
21 transactions · 19 stateful · 2026-09-30 00:14:07 UTC
Parallelism
86/100
Blocked
26%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,176,179 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w27w08w114w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0x3a663e9a…a9c5
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c7
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9c8
0x508254…98bd
6 touches
3 conflicts
0x25b1c19a…6d24
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0xd23e9468…049a
0x508254…98bd
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity