← previous blocknext block →recent activity
Analyzing
Block #84,028,431
14 transactions · 12 stateful · 2026-06-27 12:03:35 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,028,431 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w49w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb83
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xaf207244…57f7
0xd32edf…ff58
7 touches
6 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
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 0x0000000000…00001b
Audit this contract →
← previous block·next block →recent activity