← previous blocknext block →recent activity
Analyzing
Block #74,428,098
22 transactions · 19 stateful · 2026-05-14 00:25:38 UTC
Parallelism
64/100
Blocked
58%
Avg conflicts / tx
1.64
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,428,098 · 22 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
1w02w13w24w36w47w512w613w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9620e03d…6bd3
0xd32edf…ff58
15 touches
28 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0xfdd2f16c…1711
0x065c9d…c394
6 touches
3 conflicts
0xbad68552…e6bf
0x34b655…2a6f
4 touches
1 conflict
0x4d42f16e…a6c9
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xbbee74c2…567a
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
28 conflicts on slot 0x9620e03d14…a86bd3
Audit this contract →
← previous block·next block →recent activity