← previous blocknext block →recent activity
Analyzing
Block #72,366,434
30 transactions · 27 stateful · 2026-05-04 11:23:29 UTC
Parallelism
67/100
Blocked
67%
Avg conflicts / tx
1.9
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,366,434 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x839c0099…c777
0xd32edf…ff58
15 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x0d0b2509…074d
0x3bd359…433a
8 touches
6 conflicts
0xe6455d1f…1029
0x754704…b603
8 touches
6 conflicts
0x580c6fe7…0fe4
0x1b6862…e19c
8 touches
6 conflicts
0xf3981be5…2c47
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0x839c00996e…11c777
Audit this contract →
← previous block·next block →recent activity