← previous blocknext block →recent activity
Analyzing
Block #101,966,306
38 transactions · 24 stateful · 2026-09-04 18:01:03 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,966,306 · 38 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w29w010w317w020w121w222w324w231w133w436w237w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfecc5e1d…e3e5
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x42102e63…8aa6
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1d0c3193…aae4
0x3bd359…433a
6 touches
3 conflicts
0xc3baa205…f26e
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
10 conflicts on slot 0xfecc5e1d55…5fe3e5
Audit this contract →
← previous block·next block →recent activity