← previous blocknext block →recent activity
Analyzing
Block #76,529,483
31 transactions · 23 stateful · 2026-05-23 18:16:10 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,529,483 · 31 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
1w02w13w24w35w48w113w015w017w118w122w024w129w030w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3f21000…00a5
0xd32edf…ff58
9 touches
10 conflicts
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0xe75ce681…ba5f
0x188d58…ea8e
4 touches
1 conflict
0xe75ce681…ba61
0x188d58…ea8e
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
10 conflicts on slot 0xd3f210009a…1e00a5
Audit this contract →
← previous block·next block →recent activity