← previous blocknext block →recent activity
Analyzing
Block #85,908,610
26 transactions · 17 stateful · 2026-07-06 04:54:44 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,908,610 · 26 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
2w03w18w09w211w012w114w315w416w123w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x46b62326…9b3c
0xa6afd3…d132
8 touches
6 conflicts
0xa19aba84…8922
0xa6afd3…d132
8 touches
6 conflicts
0x1319a17a…a442
0xa6afd3…d132
5 touches
3 conflicts
0x1c41129b…8466
0xa6afd3…d132
5 touches
3 conflicts
0x772de411…6830
0xa6afd3…d132
5 touches
3 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity