← previous blocknext block →recent activity
Analyzing
Block #77,184,114
20 transactions · 15 stateful · 2026-05-26 18:54:36 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #77,184,114 · 20 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
1w02w14w25w16w27w18w312w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f24698c…9a5a
0xd32edf…ff58
7 touches
6 conflicts
0x6c6f37ba…c207
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x0aa885fa…a3d1
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
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 0x3f24698c97…f69a5a
Audit this contract →
← previous block·next block →recent activity