← previous blocknext block →recent activity
Analyzing
Block #98,532,750
31 transactions · 27 stateful · 2026-08-23 17:06:02 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.32
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #98,532,750 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w19w214w415w016w117w521w624w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fcd5d5e…d64c
0xd32edf…ff58
13 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x60726f3c…b5b8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9b36f19f…fa5a
0x34b655…2a6f
6 touches
3 conflicts
0xa02838a3…bc54
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
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
21 conflicts on slot 0x7fcd5d5e67…e2d64c
Audit this contract →
← previous block·next block →recent activity