← previous blocknext block →recent activity
Analyzing
Block #84,069,310
17 transactions · 15 stateful · 2026-06-27 16:35:47 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,069,310 · 17 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
1w04w05w16w27w38w410w211w512w314w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xb7baa962…ec0a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x763dd151…d9de
0xa6afd3…d132
6 touches
3 conflicts
0x5ffc25fa…b119
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: ShMonad (shMON)
6 conflicts on slot 0xd9f18d9a4a…7f141d
Audit this contract →
← previous block·next block →recent activity