← previous blocknext block →recent activity
Analyzing
Block #77,182,098
23 transactions · 19 stateful · 2026-05-26 18:41:09 UTC
Parallelism
78/100
Blocked
26%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,182,098 · 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
1w02w13w24w310w411w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55dc6200…f706
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x8b41ec8f…c2d5
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
6 conflicts on slot 0x55dc6200af…39f706
Audit this contract →
← previous block·next block →recent activity