← previous blocknext block →recent activity
Analyzing
Block #73,037,195
25 transactions · 19 stateful · 2026-05-07 13:52:05 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,037,195 · 25 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
1w02w13w24w35w46w07w010w114w217w018w121w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaaa0e24…13f3
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0x4d42f16e…a6cd
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
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 0xfaaa0e2463…eb13f3
Audit this contract →
← previous block·next block →recent activity