← previous blocknext block →recent activity
Analyzing
Block #73,688,360
16 transactions · 15 stateful · 2026-05-10 14:10:00 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,688,360 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x626336ff…6870
0xd32edf…ff58
15 touches
28 conflicts
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x17a7f697…dcb5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xc9e97522…3519
0x2a68ba…90c5
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
28 conflicts on slot 0x626336ffb1…1e6870
Audit this contract →
← previous block·next block →recent activity