← previous blocknext block →recent activity
Analyzing
Block #85,994,918
36 transactions · 24 stateful · 2026-07-06 14:30:39 UTC
Parallelism
86/100
Blocked
46%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,994,918 · 36 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
4w05w16w211w012w013w015w017w120w121w222w324w125w431w032w133w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x3181bd2d…cf15
0xa6afd3…d132
6 touches
3 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0xef02ed46…48a4
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity