← previous blocknext block →recent activity
Analyzing
Block #108,674,085
23 transactions · 22 stateful · 2026-09-28 05:59:58 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.91
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,674,085 · 23 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
1w02w03w14w25w36w07w19w210w318w319w420w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x013bb37b…eb49
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0xe8d20004…4ba6
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0002
0x125f12…a50b
12 touches
15 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0009
0x125f12…a50b
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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)
21 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity