← previous blocknext block →recent activity
Analyzing
Block #73,948,591
26 transactions · 20 stateful · 2026-05-11 19:13:10 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,948,591 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w08w110w111w012w015w016w117w018w119w220w324w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18dc6b6e…d937
0xd32edf…ff58
7 touches
6 conflicts
0x8240d70c…7c3b
0x34b655…2a6f
6 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
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 0x18dc6b6e8b…5cd937
Audit this contract →
← previous block·next block →recent activity