← previous blocknext block →recent activity
Analyzing
Block #75,107,084
10 transactions · 8 stateful · 2026-05-17 04:03:01 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,107,084 · 10 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x7c9609a1…ccce
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x55c7df79…f25c
0xd32edf…ff58
3 touches
1 conflict
0x28b59ff6…fcfe
0x065c9d…c394
2 touches
0 conflicts
0x4aa4f53b…899f
0x188d58…ea8e
2 touches
0 conflicts
0x4aa4f53b…89a1
0x188d58…ea8e
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: USDC (USDC)
3 conflicts on slot 0xa1087a5ca6…0a66c4
Audit this contract →
← previous block·next block →recent activity