← previous blocknext block →recent activity
Analyzing
Block #74,566,145
23 transactions · 18 stateful · 2026-05-14 15:50:14 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,566,145 · 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
1w02w13w24w35w46w57w611w113w016w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc80c56bd…63f5
0xd32edf…ff58
13 touches
21 conflicts
0xbad68552…e6bf
0x34b655…2a6f
6 touches
3 conflicts
0x1045386d…cb8c
0x1b6862…e19c
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0xc80c56bd8c…8063f5
Audit this contract →
← previous block·next block →recent activity