← previous blocknext block →recent activity
Analyzing
Block #77,185,162
10 transactions · 8 stateful · 2026-05-26 19:01:36 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,185,162 · 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
1w02w16w27w38w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc51d3663…0f45
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xe2e94dfa…5026
0x2a68ba…90c5
4 touches
1 conflict
0x2dc020c7…0697
0xc8689a…ee79
4 touches
1 conflict
0xd71a331e…42ea
0xa6afd3…d132
3 touches
1 conflict
0x595839b9…ca61
0x1d1325…2305
2 touches
0 conflicts
0x7aa91b8f…d070
0x1d1325…2305
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: Kuru Exchange: Market-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity