← previous blocknext block →recent activity
Analyzing
Block #85,855,552
36 transactions · 22 stateful · 2026-07-05 23:01:22 UTC
Parallelism
89/100
Blocked
41%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,855,552 · 36 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w16w07w112w013w115w217w218w021w322w223w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6005a3c4…a833
0x065c9d…c394
7 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xe88b9730…4098
0xd32edf…ff58
5 touches
3 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
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-MON/USDC
6 conflicts on slot 0x6005a3c423…1ea833
Audit this contract →
← previous block·next block →recent activity