← previous blocknext block →recent activity
Analyzing
Block #98,538,030
34 transactions · 33 stateful · 2026-08-23 17:33:28 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,538,030 · 34 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w19w010w112w013w115w216w317w020w224w327w128w232w033w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x41469894…598f
0x34b655…2a6f
6 touches
3 conflicts
0x41469894…5990
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xd60e2d70…0c7e
0xd32edf…ff58
5 touches
3 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)
3 conflicts on slot 0x0000000000…00001d
Audit this contract →
← previous block·next block →recent activity