← previous blocknext block →recent activity
Analyzing
Block #75,478,216
33 transactions · 14 stateful · 2026-05-18 21:23:01 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #75,478,216 · 33 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
1w02w17w113w014w116w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4be4d91…287e
0xd32edf…ff58
13 touches
21 conflicts
0x66312019…f62e
0xe7cd86…c82d
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb80
0x1b6862…e19c
4 touches
1 conflict
0x6237f1a7…2f59
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x47bae1…7568
4 touches
1 conflict
0x00000000…0002
0x47bae1…7568
4 touches
1 conflict
0x00000000…0004
0x47bae1…7568
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
21 conflicts on slot 0xe4be4d9103…3a287e
Audit this contract →
← previous block·next block →recent activity