← previous blocknext block →recent activity
Analyzing
Block #90,624,935
20 transactions · 17 stateful · 2026-07-27 00:10:04 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,624,935 · 20 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
2w06w07w18w212w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x0f7df08f…cad4
0xa6afd3…d132
6 touches
3 conflicts
0x17e90565…d957
0xa6afd3…d132
6 touches
3 conflicts
0x3f314024…133e
0x065c9d…c394
2 touches
0 conflicts
0x7bbaef50…5f39
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0x90d9c75d…d61e
0x065c9d…c394
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity