← previous blocknext block →recent activity
Analyzing
Block #108,684,773
16 transactions · 16 stateful · 2026-09-28 06:53:51 UTC
Parallelism
69/100
Blocked
56%
Avg conflicts / tx
1.31
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,684,773 · 16 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
1w02w13w24w35w08w29w110w212w013w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26bb6db7…f85c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe512fe17…fbaf
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
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)
6 conflicts on slot 0x26bb6db701…d0f85c
Audit this contract →
← previous block·next block →recent activity