← previous blocknext block →recent activity
Analyzing
Block #99,097,960
31 transactions · 27 stateful · 2026-08-25 17:06:08 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,097,960 · 31 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
1w02w13w27w110w011w112w213w117w019w320w422w126w229w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7373b140…55c1
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
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 0x7373b1403d…b055c1
Audit this contract →
← previous block·next block →recent activity