← previous blocknext block →recent activity
Analyzing
Block #99,976,195
32 transactions · 27 stateful · 2026-08-28 19:00:28 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,976,195 · 32 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
1w02w17w08w210w112w216w217w318w319w420w422w224w025w126w431w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeebad79e…965f
0xd32edf…ff58
9 touches
10 conflicts
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xfa324e43…8896
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xeebad79e52…87965f
Audit this contract →
← previous block·next block →recent activity