← previous blocknext block →recent activity
Analyzing
Block #85,105,256
16 transactions · 9 stateful · 2026-07-02 11:42:42 UTC
Parallelism
88/100
Blocked
22%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,105,256 · 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
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36d366fe…7adc
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9cf5ac50…1be9
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x03d4f4ad…f6df
0x065c9d…c394
2 touches
0 conflicts
0x0e681232…f0ba
0x065c9d…c394
2 touches
0 conflicts
0x6a1d1443…a6db
0x065c9d…c394
2 touches
0 conflicts
0xa91552b6…80ed
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
1 conflict on slot 0x36d366fe30…fe7adc
Audit this contract →
← previous block·next block →recent activity