← previous blocknext block →recent activity
Analyzing
Block #96,603,992
35 transactions · 27 stateful · 2026-08-16 22:02:57 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
1.71
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,603,992 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w611w718w621w324w725w430w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001e
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002e
0x1b6862…e19c
14 touches
21 conflicts
0x73912233…4588
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0xdcc13a9a…c1da
0xd32edf…ff58
13 touches
21 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)
21 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity