← previous blocknext block →recent activity
Analyzing
Block #108,496,243
39 transactions · 31 stateful · 2026-09-27 15:04:23 UTC
Parallelism
62/100
Blocked
71%
Avg conflicts / tx
2.59
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #108,496,243 · 39 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w28w313w414w515w616w718w220w121w822w123w926w1027w1134w1035w1136w1237w1338w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60768ed0…68fb
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x91ecc547…33ef
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 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
66 conflicts on slot 0x60768ed02c…7a68fb
Audit this contract →
← previous block·next block →recent activity