← previous blocknext block →recent activity
Analyzing
Block #75,572,725
28 transactions · 15 stateful · 2026-05-19 08:01:17 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #75,572,725 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w711w316w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3daa5a5…788b
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0000
0x04ddf6…7f33
4 touches
1 conflict
0xaeabffea…5dd4
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0002
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
4 touches
1 conflict
0x6901bef4…4a69
0x754704…b603
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x0d73bf…be07
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
36 conflicts on slot 0xc3daa5a508…32788b
Audit this contract →
← previous block·next block →recent activity