← previous blocknext block →recent activity
Analyzing
Block #108,940,365
31 transactions · 22 stateful · 2026-09-29 04:23:53 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.81
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #108,940,365 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16d5b6ec…5258
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0056
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0040
0x1b6862…e19c
16 touches
28 conflicts
0x2bbc0cfb…c2c0
0x1b6862…e19c
16 touches
28 conflicts
0x6cbcefbb…51cb
0x1b6862…e19c
16 touches
28 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
55 conflicts on slot 0x16d5b6ec2e…e65258
Audit this contract →
← previous block·next block →recent activity