← previous blocknext block →recent activity
Analyzing
Block #99,451,269
22 transactions · 21 stateful · 2026-08-26 22:44:22 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,451,269 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w110w011w114w315w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f28fb99…3d30
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x70d81211…f49f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 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 0x0f28fb99c9…3f3d30
Audit this contract →
← previous block·next block →recent activity