← previous blocknext block →recent activity
Analyzing
Block #99,615,679
28 transactions · 26 stateful · 2026-08-27 12:38:01 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
1.21
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,615,679 · 28 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
1w02w13w24w05w37w09w410w522w624w827w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35801c67…bcc1
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0x89612b67…3704
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 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 0x35801c670c…33bcc1
Audit this contract →
← previous block·next block →recent activity