← previous blocknext block →recent activity
Analyzing
Block #108,961,767
16 transactions · 15 stateful · 2026-09-29 06:12:15 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,961,767 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w39w010w111w213w014w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc52e608d…305c
0xd32edf…ff58
9 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x8b780b26…f5ff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0057
0x1b6862…e19c
6 touches
3 conflicts
0x063eca74…c2e2
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0xc52e608d3c…1c305c
Audit this contract →
← previous block·next block →recent activity