← previous blocknext block →recent activity
Analyzing
Block #108,961,399
22 transactions · 20 stateful · 2026-09-29 06:10:21 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
1.36
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,961,399 · 22 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
2w03w14w25w36w47w58w620w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3041738…a693
0xd32edf…ff58
13 touches
21 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
10 touches
10 conflicts
0x928d6b23…5373
0x1b6862…e19c
10 touches
10 conflicts
0xc9a59d29…f159
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xa7798c51…8be7
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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: FastLane: FastLaneAuctionHandler
21 conflicts on slot 0xa304173831…15a693
Audit this contract →
← previous block·next block →recent activity