← previous blocknext block →recent activity
Analyzing
Block #74,788,617
24 transactions · 19 stateful · 2026-05-15 16:36:30 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,788,617 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w011w112w013w114w415w016w117w018w119w121w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeb82c7e0…5f6e
0xd32edf…ff58
9 touches
10 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
6 touches
3 conflicts
0x2d0de12e…3972
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x512705a6…3930
0x065c9d…c394
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
10 conflicts on slot 0xeb82c7e04b…3d5f6e
Audit this contract →
← previous block·next block →recent activity