← previous blocknext block →recent activity
Analyzing
Block #108,397,220
26 transactions · 26 stateful · 2026-09-27 06:45:56 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,397,220 · 26 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
1w02w13w24w35w46w48w09w110w516w517w619w622w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xf5dc501b…831c
0x34b655…2a6f
10 touches
10 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xac79a0c7…be11
0x1b6862…e19c
10 touches
10 conflicts
0xef8bde88…a8a3
0xd32edf…ff58
9 touches
10 conflicts
0x2e84bea1…20bc
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001a
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 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity