← previous blocknext block →recent activity
Analyzing
Block #75,936,473
23 transactions · 20 stateful · 2026-05-21 00:26:48 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,936,473 · 23 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
1w02w04w15w28w29w010w111w212w014w115w216w317w422w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ea8cbb3…f3d3
0xd32edf…ff58
9 touches
10 conflicts
0x08943ea2…ed03
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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 0x5ea8cbb3f6…4ff3d3
Audit this contract →
← previous block·next block →recent activity