← previous blocknext block →recent activity
Analyzing
Block #72,971,082
30 transactions · 23 stateful · 2026-05-07 06:32:02 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,971,082 · 30 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
1w02w13w24w35w46w57w613w418w724w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x507c575f…a5db
0xd32edf…ff58
15 touches
28 conflicts
0x251861eb…78fd
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
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
28 conflicts on slot 0x507c575f63…6da5db
Audit this contract →
← previous block·next block →recent activity