← previous blocknext block →recent activity
Analyzing
Block #75,676,854
23 transactions · 19 stateful · 2026-05-19 19:37:05 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,676,854 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w513w414w518w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a60c65b…f0d7
0xd32edf…ff58
11 touches
15 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0xcaa41b23…275a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
15 conflicts on slot 0x5a60c65b39…41f0d7
Audit this contract →
← previous block·next block →recent activity