← previous blocknext block →recent activity
Analyzing
Block #99,084,867
21 transactions · 20 stateful · 2026-08-25 16:00:07 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,084,867 · 21 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
1w02w13w26w08w39w410w011w112w016w319w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e04662b…0da1
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
10 touches
10 conflicts
0x94cda123…83c6
0xd32edf…ff58
9 touches
10 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)
10 conflicts on slot 0x3e04662bca…090da1
Audit this contract →
← previous block·next block →recent activity