← previous blocknext block →recent activity
Analyzing
Block #74,788,847
30 transactions · 21 stateful · 2026-05-15 16:38:02 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,788,847 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w17w28w312w413w417w018w019w122w123w224w325w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a5633e2…5b58
0xd32edf…ff58
11 touches
15 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
10 touches
10 conflicts
0x41755291…977f
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x7a0f243e…fc2e
0x065c9d…c394
5 touches
4 conflicts
0x8d9e9f99…d20e
0x065c9d…c394
5 touches
3 conflicts
0x11f25e19…8bb1
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
15 conflicts on slot 0x1a5633e2a5…9e5b58
Audit this contract →
← previous block·next block →recent activity