← previous blocknext block →recent activity
Analyzing
Block #90,321,412
16 transactions · 15 stateful · 2026-07-25 22:31:10 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
1.13
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #90,321,412 · 16 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
1w02w13w24w39w010w111w212w313w415w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fdca90b…c6c7
0xd32edf…ff58
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3638288c…cb00
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xa9af9157…5a6e
0x34b655…2a6f
6 touches
3 conflicts
0xfed09e59…a493
0x34b655…2a6f
6 touches
3 conflicts
0x8299fe6c…5752
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 0x6fdca90bd0…1bc6c7
Audit this contract →
← previous block·next block →recent activity