← previous blocknext block →recent activity
Analyzing
Block #75,834,277
50 transactions · 35 stateful · 2026-05-20 13:05:00 UTC
Parallelism
58/100
Blocked
69%
Avg conflicts / tx
4.44
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #75,834,277 · 50 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1528w1630w1735w1836w1937w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f55aab7…5fb7
0xd32edf…ff58
41 touches
210 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0000
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0003
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0004
0x63e48b…53f2
10 touches
10 conflicts
0x9a555477…19a8
0x754704…b603
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c6
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
210 conflicts on slot 0x0f55aab768…575fb7
Audit this contract →
← previous block·next block →recent activity