← previous blocknext block →recent activity
Analyzing
Block #76,462,441
32 transactions · 14 stateful · 2026-05-23 10:49:44 UTC
Parallelism
84/100
Blocked
43%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,462,441 · 32 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
4w05w16w27w316w120w430w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cb8833e…23d5
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x1f8a126c…9aa5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x8d0e98f3…7ba0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xddd20e39…d524
0x34b655…2a6f
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 0x4cb8833e1b…6d23d5
Audit this contract →
← previous block·next block →recent activity