← previous blocknext block →recent activity
Analyzing
Block #76,141,908
19 transactions · 16 stateful · 2026-05-21 23:15:28 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,141,908 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w19w611w616w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0bb7d8f…f29f
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xf3d7a307…4d63
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c4
0x1b6862…e19c
10 touches
10 conflicts
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
15 conflicts on slot 0xb0bb7d8f0b…6bf29f
Audit this contract →
← previous block·next block →recent activity