← previous blocknext block →recent activity
Analyzing
Block #108,503,398
24 transactions · 20 stateful · 2026-09-27 15:40:25 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,503,398 · 24 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
5w08w09w110w012w115w219w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26176835…e354
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x74e485b1…d380
0x34b655…2a6f
6 touches
3 conflicts
0xd7618c74…ccf7
0x34b655…2a6f
6 touches
3 conflicts
0x085df2c1…305a
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0x26176835a1…a8e354
Audit this contract →
← previous block·next block →recent activity