← previous blocknext block →recent activity
Analyzing
Block #73,216,580
10 transactions · 8 stateful · 2026-05-08 09:45:35 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,216,580 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf284961b…c167
0xd32edf…ff58
5 touches
3 conflicts
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x145619c0…7bc1
0x065c9d…c394
2 touches
0 conflicts
0x29a03b22…3caf
0x065c9d…c394
2 touches
0 conflicts
0x3a9af0c6…a255
0x065c9d…c394
2 touches
0 conflicts
0x3c38f7e4…d946
0x065c9d…c394
2 touches
0 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
3 conflicts on slot 0xf284961b2a…3cc167
Audit this contract →
← previous block·next block →recent activity