← previous blocknext block →recent activity
Analyzing
Block #72,366,440
21 transactions · 20 stateful · 2026-05-04 11:23:32 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,366,440 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w16w07w38w49w510w612w213w116w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd333338…a5e5
0xd32edf…ff58
13 touches
21 conflicts
0x4979282b…2933
0x1b6862…e19c
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…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
21 conflicts on slot 0xdd333338ae…e1a5e5
Audit this contract →
← previous block·next block →recent activity