← previous blocknext block →recent activity
Analyzing
Block #73,377,617
20 transactions · 16 stateful · 2026-05-09 03:36:56 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
2.25
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,377,617 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w711w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92283c2a…f8b5
0xd32edf…ff58
19 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x0a85a226…83c0
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
45 conflicts on slot 0x92283c2add…e5f8b5
Audit this contract →
← previous block·next block →recent activity