← previous blocknext block →recent activity
Analyzing
Block #89,403,390
15 transactions · 12 stateful · 2026-07-22 10:22:41 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,403,390 · 15 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
1w02w13w24w35w210w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc34a381…c6f4
0xd32edf…ff58
9 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x0a35ee29…19f6
0x065c9d…c394
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe783dfa4…5499
0x1b6862…e19c
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x4f33dcd8…95aa
0x40c49f…2af0
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 0xdc34a38101…e3c6f4
Audit this contract →
← previous block·next block →recent activity