← previous blocknext block →recent activity
Analyzing
Block #76,237,014
24 transactions · 16 stateful · 2026-05-22 09:49:04 UTC
Parallelism
75/100
Blocked
56%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,237,014 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w110w515w416w519w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd36e2fd9…c995
0xd32edf…ff58
9 touches
10 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd9e09526…959c
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x91220b8f…7a08
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 0xd36e2fd915…2fc995
Audit this contract →
← previous block·next block →recent activity