← previous blocknext block →recent activity
Analyzing
Block #108,276,333
15 transactions · 14 stateful · 2026-09-26 20:37:36 UTC
Parallelism
47/100
Blocked
57%
Avg conflicts / tx
1.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,276,333 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w610w714w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0018
0x1b6862…e19c
16 touches
28 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
16 touches
28 conflicts
0xd48dc627…a892
0xd32edf…ff58
15 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x74e485b1…d380
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1e2721…7805
2 touches
0 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)
28 conflicts on slot 0xd9f18d9a4a…7f141d
Audit this contract →
← previous block·next block →recent activity