← previous blocknext block →recent activity
Analyzing
Block #74,763,954
39 transactions · 25 stateful · 2026-05-15 13:51:30 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,763,954 · 39 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w112w013w115w223w334w035w136w237w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f613c78…1672
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
15 conflicts on slot 0x6f613c78d8…9c1672
Audit this contract →
← previous block·next block →recent activity