← previous blocknext block →recent activity
Analyzing
Block #85,131,169
21 transactions · 19 stateful · 2026-07-02 14:35:59 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,131,169 · 21 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
1w04w06w07w19w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0x2406ccf7…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x6ca32a09…4e48
0x34b655…2a6f
4 touches
1 conflict
0x7b2ff50b…8f84
0x34b655…2a6f
4 touches
1 conflict
0x9858faee…2e6d
0x34b655…2a6f
4 touches
1 conflict
0xed59b1cd…8509
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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 0x987aeb55c2…370e2a
Audit this contract →
← previous block·next block →recent activity