← previous blocknext block →recent activity
Analyzing
Block #73,687,187
24 transactions · 19 stateful · 2026-05-10 14:02:03 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,687,187 · 24 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
1w02w13w24w37w210w412w013w114w015w116w317w422w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c576e6f…7d5e
0xd32edf…ff58
9 touches
10 conflicts
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x3e733ae4…4598
0x34b655…2a6f
8 touches
6 conflicts
0xc9e97522…3519
0x2a68ba…90c5
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
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
10 conflicts on slot 0x8c576e6f3c…187d5e
Audit this contract →
← previous block·next block →recent activity