← previous blocknext block →recent activity
Analyzing
Block #74,325,802
33 transactions · 20 stateful · 2026-05-13 13:05:01 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,325,802 · 33 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
1w02w13w24w35w46w514w515w625w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x213b007e…c418
0xd32edf…ff58
13 touches
21 conflicts
0x4dd1db39…a994
0x188d58…ea8e
6 touches
3 conflicts
0x4dd1db39…a996
0x188d58…ea8e
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
6 touches
3 conflicts
0x4dd1db39…a997
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
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 0x213b007e1a…eec418
Audit this contract →
← previous block·next block →recent activity