← previous blocknext block →recent activity
Analyzing
Block #72,458,623
22 transactions · 15 stateful · 2026-05-04 21:37:51 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #72,458,623 · 22 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
1w04w06w18w210w111w312w413w214w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fe501fc…dd13
0xd32edf…ff58
13 touches
21 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xd38eef67…6a20
0x065c9d…c394
3 touches
1 conflict
0xeb1bf109…3d8f
0x065c9d…c394
3 touches
1 conflict
0x2343b4c2…d6bb
0x34b655…2a6f
2 touches
0 conflicts
0x38dee07f…7598
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 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 0x2fe501fcfe…f8dd13
Audit this contract →
← previous block·next block →recent activity