← previous blocknext block →recent activity
Analyzing
Block #77,352,366
30 transactions · 21 stateful · 2026-05-27 13:38:45 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,352,366 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w27w09w112w215w216w321w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x355841d5…50b6
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
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…001d
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 0x355841d5cb…9350b6
Audit this contract →
← previous block·next block →recent activity