← previous blocknext block →recent activity
Analyzing
Block #108,961,907
22 transactions · 19 stateful · 2026-09-29 06:13:00 UTC
Parallelism
91/100
Blocked
32%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,961,907 · 22 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w18w09w110w011w114w015w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36dfe42e…23b6
0xa6afd3…d132
4 touches
1 conflict
0x1f103912…aca3
0xa6afd3…d132
4 touches
1 conflict
0x2912965a…d76a
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x604438d3…4638
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
1 conflict on slot 0x36dfe42e66…0c23b6
Audit this contract →
← previous block·next block →recent activity