← previous blocknext block →recent activity
Analyzing
Block #73,037,685
22 transactions · 13 stateful · 2026-05-07 13:55:20 UTC
Parallelism
68/100
Blocked
46%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,037,685 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w110w212w314w415w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe536d670…c836
0xd32edf…ff58
13 touches
21 conflicts
0x6ea8fa8d…3ddb
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xad092ae6…b421
0x754704…b603
4 touches
1 conflict
0x4d10fad4…b8e0
0x3bd359…433a
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
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
21 conflicts on slot 0xe536d670cc…b1c836
Audit this contract →
← previous block·next block →recent activity