← previous blocknext block →recent activity
Analyzing
Block #75,792,105
21 transactions · 19 stateful · 2026-05-20 08:23:41 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,792,105 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w28w010w211w312w414w015w116w217w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00179f2b…e6f1
0xd32edf…ff58
9 touches
10 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
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 0x00179f2b3b…b5e6f1
Audit this contract →
← previous block·next block →recent activity