← previous blocknext block →recent activity
Analyzing
Block #72,282,933
25 transactions · 23 stateful · 2026-05-04 02:06:30 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,282,933 · 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
1w02w13w24w35w27w08w39w412w013w114w217w120w221w323w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55e0f406…2afc
0xd32edf…ff58
9 touches
10 conflicts
0xffe431af…8faa
0x065c9d…c394
8 touches
6 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x55e0f40620…942afc
Audit this contract →
← previous block·next block →recent activity