← previous blocknext block →recent activity
Analyzing
Block #75,700,724
25 transactions · 17 stateful · 2026-05-19 22:15:35 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,700,724 · 25 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
2w03w14w25w36w47w515w621w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x100ed27a…abd7
0xd32edf…ff58
13 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x11333508…2819
0x010592…1c83
2 touches
0 conflicts
0xa4248a13…52c3
0x010592…1c83
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 0x100ed27a15…8aabd7
Audit this contract →
← previous block·next block →recent activity