← previous blocknext block →recent activity
Analyzing
Block #74,898,508
28 transactions · 21 stateful · 2026-05-16 04:49:25 UTC
Parallelism
75/100
Blocked
52%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,898,508 · 28 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
1w02w13w24w35w48w49w010w111w213w014w516w617w018w126w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38353aef…030d
0xd32edf…ff58
9 touches
10 conflicts
0x12309510…0ac2
0x000000…012a
6 touches
3 conflicts
0x0d0b2509…074d
0x3bd359…433a
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xe6455d1f…1029
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
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
10 conflicts on slot 0x38353aef4b…f6030d
Audit this contract →
← previous block·next block →recent activity