← previous blocknext block →recent activity
Analyzing
Block #108,512,630
30 transactions · 27 stateful · 2026-09-27 16:26:53 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,512,630 · 30 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
1w02w13w24w35w46w57w620w421w523w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fa95e2b…9cfc
0xd32edf…ff58
15 touches
28 conflicts
0x17a7f697…dcb6
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x3a663e9a…a9c8
0x508254…98bd
6 touches
3 conflicts
0x3a663e9a…a9cb
0x508254…98bd
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
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
28 conflicts on slot 0x1fa95e2b1e…d09cfc
Audit this contract →
← previous block·next block →recent activity