← previous blocknext block →recent activity
Analyzing
Block #72,311,041
18 transactions · 15 stateful · 2026-05-04 05:14:31 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,311,041 · 18 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
1w02w14w06w17w08w19w210w311w012w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e74623f…bd86
0xd32edf…ff58
9 touches
10 conflicts
0x9fb7ac91…e49a
0x065c9d…c394
4 touches
1 conflict
0x968bdacb…f461
0x2a68ba…90c5
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0x0fa5e7bf…a4da
0x34b655…2a6f
4 touches
1 conflict
0x5728edaf…f1d4
0x34b655…2a6f
4 touches
1 conflict
0x578e7f66…1b56
0x34b655…2a6f
4 touches
1 conflict
0x57de3828…3fbb
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 0x6e74623ff5…bfbd86
Audit this contract →
← previous block·next block →recent activity