← previous blocknext block →recent activity
Analyzing
Block #76,482,192
23 transactions · 22 stateful · 2026-05-23 13:01:21 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,482,192 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w210w011w012w113w115w316w419w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3afb222…4d17
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x99a4d286…ad43
0xa6afd3…d132
6 touches
3 conflicts
0x781a2c9b…f540
0x34b655…2a6f
6 touches
3 conflicts
0x10d80fee…dbda
0x1d1325…2305
4 touches
1 conflict
0x3484c9df…bfd5
0x1d1325…2305
4 touches
1 conflict
0x8cf3d245…1d0d
0x1d1325…2305
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: Kuru Exchange: Market-WETH/USDC
6 conflicts on slot 0xc3afb2229f…7f4d17
Audit this contract →
← previous block·next block →recent activity