← previous blocknext block →recent activity
Analyzing
Block #108,611,537
16 transactions · 16 stateful · 2026-09-28 00:44:57 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.81
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,611,537 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x358e42ad…a63a
0xd32edf…ff58
15 touches
28 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xaea7127c…0134
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: FastLane: FastLaneAuctionHandler
28 conflicts on slot 0x358e42ad31…7ea63a
Audit this contract →
← previous block·next block →recent activity