← previous blocknext block →recent activity
Analyzing
Block #102,250,584
26 transactions · 25 stateful · 2026-09-05 18:01:57 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,250,584 · 26 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
1w02w13w25w36w28w012w217w018w019w121w123w424w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1da7723c…80ae
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x4ab70ccd…2683
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xd0b0f077…f1d4
0xd32edf…ff58
5 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
4 touches
1 conflict
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 0x1da7723cc0…4180ae
Audit this contract →
← previous block·next block →recent activity