← previous blocknext block →recent activity
Analyzing
Block #108,671,935
23 transactions · 19 stateful · 2026-09-28 05:49:09 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
0.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,671,935 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w38w09w112w413w114w215w316w517w618w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd25997d0…a683
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x1fff397e…43c5
0x34b655…2a6f
8 touches
6 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
8 touches
6 conflicts
0xdddee937…a5f1
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x300f5f5c…606b
0x065c9d…c394
5 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 0xd25997d049…f6a683
Audit this contract →
← previous block·next block →recent activity