← previous blocknext block →recent activity
Analyzing
Block #108,575,091
33 transactions · 22 stateful · 2026-09-27 21:41:29 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,575,091 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w010w012w115w216w117w018w120w321w122w224w330w332w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a9cc56…00f3
0xd32edf…ff58
7 touches
6 conflicts
0xc7679110…572d
0x34b655…2a6f
6 touches
3 conflicts
0x09baf10c…d5cf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x99a9cc56d4…0c00f3
Audit this contract →
← previous block·next block →recent activity