← previous blocknext block →recent activity
Analyzing
Block #108,960,690
24 transactions · 21 stateful · 2026-09-29 06:06:42 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
1.71
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,960,690 · 24 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
3w04w05w16w17w28w39w410w511w612w414w517w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33d61de7…6f30
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002e
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0057
0x1b6862…e19c
12 touches
15 conflicts
0x5a55b368…bb81
0x1b6862…e19c
12 touches
15 conflicts
0xe937b6bc…8a5a
0x1b6862…e19c
12 touches
15 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 0x33d61de72b…f46f30
Audit this contract →
← previous block·next block →recent activity