← previous blocknext block →recent activity
Analyzing
Block #74,606,454
25 transactions · 20 stateful · 2026-05-14 20:20:24 UTC
Parallelism
68/100
Blocked
65%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,606,454 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w416w517w618w719w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f210e0b…5230
0xd32edf…ff58
15 touches
28 conflicts
0x928d6b23…5374
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
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
28 conflicts on slot 0x8f210e0bcc…9b5230
Audit this contract →
← previous block·next block →recent activity