← previous blocknext block →recent activity
Analyzing
Block #72,209,858
22 transactions · 18 stateful · 2026-05-03 17:55:28 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,209,858 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w614w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6c5da40…a8a1
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xe01158fd…f983
0x1b6862…e19c
6 touches
3 conflicts
0x74e71984…ae90
0x2a68ba…90c5
6 touches
3 conflicts
0x0d00f082…a015
0x065c9d…c394
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
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
21 conflicts on slot 0xd6c5da40b2…98a8a1
Audit this contract →
← previous block·next block →recent activity