← previous blocknext block →recent activity
Analyzing
Block #74,418,817
40 transactions · 23 stateful · 2026-05-13 23:23:53 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.97
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,418,817 · 40 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
1w02w13w26w37w48w510w616w131w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c37b351…0285
0xd32edf…ff58
15 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1c389468…6b0e
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x00000000…0012
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 0x6c37b3517e…d10285
Audit this contract →
← previous block·next block →recent activity