← previous blocknext block →recent activity
Analyzing
Block #75,943,680
28 transactions · 20 stateful · 2026-05-21 01:14:48 UTC
Parallelism
86/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,943,680 · 28 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w18w212w113w014w116w017w118w221w225w327w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xa793dc81…7ef1
0xd32edf…ff58
5 touches
3 conflicts
0x729c91b8…9538
0x188d58…ea8e
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x5b4dd22f…be7f
0x34b655…2a6f
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
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: USDC (USDC)
6 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity