← previous blocknext block →recent activity
Analyzing
Block #85,780,408
21 transactions · 11 stateful · 2026-07-05 14:40:42 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,780,408 · 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
1w02w06w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e352acf…dfdb
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd99b3b64…1c95
0x34b655…2a6f
4 touches
1 conflict
0x20de0a9c…2d5c
0x065c9d…c394
3 touches
1 conflict
0x230a90aa…0f5c
0x065c9d…c394
3 touches
1 conflict
0xd9a92b6a…01dc
0x34b655…2a6f
3 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
1 conflict on slot 0x6e352acf48…5edfdb
Audit this contract →
← previous block·next block →recent activity