← previous blocknext block →recent activity
Analyzing
Block #76,318,942
23 transactions · 20 stateful · 2026-05-22 18:54:14 UTC
Parallelism
70/100
Blocked
55%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,318,942 · 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
1w02w13w04w25w36w47w58w09w110w211w312w613w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3657841…0366
0xd32edf…ff58
9 touches
10 conflicts
0x99a21305…dffc
0x2a68ba…90c5
9 touches
10 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0xc3657841a8…110366
Audit this contract →
← previous block·next block →recent activity