← previous blocknext block →recent activity
Analyzing
Block #85,840,717
20 transactions · 15 stateful · 2026-07-05 21:22:26 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,840,717 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w27w38w09w110w211w412w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x81608b7a…80bd
0xd32edf…ff58
9 touches
10 conflicts
0x6af306bb…2e81
0x3bd359…433a
8 touches
6 conflicts
0x1c354dc0…96de
0x754704…b603
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: ShMonad (shMON)
10 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity