← previous blocknext block →recent activity
Analyzing
Block #85,968,677
16 transactions · 14 stateful · 2026-07-06 11:35:15 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,968,677 · 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
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0x3a0e17df…836f
0x065c9d…c394
3 touches
1 conflict
0x3dfca3ae…bcf5
0x065c9d…c394
3 touches
1 conflict
0xe5bb3628…e5e8
0x34b655…2a6f
2 touches
0 conflicts
0x690117b9…2820
0x3bd359…433a
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x27f4e3f7…a81e
0x754704…b603
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-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity