← previous blocknext block →recent activity
Analyzing
Block #72,972,489
38 transactions · 29 stateful · 2026-05-07 06:41:23 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.95
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,972,489 · 38 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w616w718w819w920w1025w135w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x300e3aae…f164
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd025d7d7…f05a
0x3bd359…433a
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
66 conflicts on slot 0x300e3aaed3…f5f164
Audit this contract →
← previous block·next block →recent activity