← previous blocknext block →recent activity
Analyzing
Block #76,668,533
10 transactions · 9 stateful · 2026-05-24 09:42:07 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,668,533 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86a35e38…e53b
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xb1f7f6eb…f44d
0x754704…b603
4 touches
1 conflict
0x0ee4479e…fb6c
0x065c9d…c394
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x81a7ba4d…8c4b
0x23c26b…7777
2 touches
0 conflicts
0x08fdca0b…4abf
0x3bd359…433a
2 touches
0 conflicts
0x5eefd705…3047
0x3bd359…433a
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)
1 conflict on slot 0x86a35e3818…6ce53b
Audit this contract →
← previous block·next block →recent activity