← previous blocknext block →recent activity
Analyzing
Block #109,134,419
25 transactions · 21 stateful · 2026-09-29 20:43:34 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.68
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,134,419 · 25 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
1w02w15w06w17w29w310w011w314w116w417w220w021w222w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc618f342…021b
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xca7cef46…1bee
0x34b655…2a6f
5 touches
3 conflicts
0x676f9f01…a8ac
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0af6e2ce…75f3
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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0xc618f34230…71021b
Audit this contract →
← previous block·next block →recent activity