← previous blocknext block →recent activity
Analyzing
Block #85,816,307
35 transactions · 27 stateful · 2026-07-05 18:39:56 UTC
Parallelism
86/100
Blocked
56%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,816,307 · 35 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
1w02w13w24w35w48w09w110w113w214w319w320w421w228w429w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6cc7de8…0b4a
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0000
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0003
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0004
0x63e48b…53f2
10 touches
10 conflicts
0x9a555477…19a8
0x754704…b603
10 touches
10 conflicts
0x715748d5…0172
0xd32edf…ff58
9 touches
10 conflicts
0xf8480e2a…dff5
0x1b6862…e19c
8 touches
6 conflicts
0xf91b744e…9117
0x754704…b603
8 touches
6 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: Wrapped MON (WMON)
10 conflicts on slot 0xf6cc7de8cb…7d0b4a
Audit this contract →
← previous block·next block →recent activity