← previous blocknext block →recent activity
Analyzing
Block #109,143,140
17 transactions · 12 stateful · 2026-09-29 21:27:27 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #109,143,140 · 17 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
1w03w04w06w18w111w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xcd92ceb8…b9d2
0xa6afd3…d132
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x5c2a2fdd…35c9
0xa6afd3…d132
4 touches
1 conflict
0xc4744aa9…fd43
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
4 touches
1 conflict
0xb05cd4f5…73d0
0x34ae4d…3fc5
2 touches
0 conflicts
0x1ff3c3e0…3ce5
0x34b655…2a6f
2 touches
0 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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity