← previous blocknext block →recent activity
Analyzing
Block #75,734,241
22 transactions · 14 stateful · 2026-05-20 01:58:48 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,734,241 · 22 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
1w03w18w010w011w112w113w214w315w417w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26a97c8f…756f
0xd32edf…ff58
13 touches
21 conflicts
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x00000000…0003
0xd5b70d…615b
4 touches
1 conflict
0xd2a67666…668a
0x065c9d…c394
3 touches
1 conflict
0x4014fc3c…33ad
0x065c9d…c394
3 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
21 conflicts on slot 0x26a97c8ff4…7c756f
Audit this contract →
← previous block·next block →recent activity