← previous blocknext block →recent activity
Analyzing
Block #73,674,164
18 transactions · 14 stateful · 2026-05-10 12:34:10 UTC
Parallelism
72/100
Blocked
43%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,674,164 · 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
1w02w13w07w28w09w112w313w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67044ec5…7629
0xd32edf…ff58
7 touches
6 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xa4929cc3…a396
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x143dba04…1b98
0x8d66a4…3095
4 touches
1 conflict
0x1e451306…7993
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d19b
0x8d66a4…3095
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
6 conflicts on slot 0x67044ec5ed…b67629
Audit this contract →
← previous block·next block →recent activity