← previous blocknext block →recent activity
Analyzing
Block #92,014,524
16 transactions · 15 stateful · 2026-07-31 20:43:57 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,014,524 · 16 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
1w02w04w16w17w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x4863e718…b481
0x7b9256…1fb2
4 touches
1 conflict
0x4863e718…b482
0x7b9256…1fb2
4 touches
1 conflict
0xa6a87395…0dad
0x7b9256…1fb2
4 touches
1 conflict
0xa6a87395…0dae
0x7b9256…1fb2
4 touches
1 conflict
0xa6a87395…0db1
0x7b9256…1fb2
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity