← previous blocknext block →recent activity
Analyzing
Block #107,442,393
46 transactions · 43 stateful · 2026-09-23 22:38:14 UTC
Parallelism
65/100
Blocked
77%
Avg conflicts / tx
3.24
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #107,442,393 · 46 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w16w27w08w19w210w311w412w513w614w715w816w917w1025w626w728w129w1132w1235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0012
0x1b6862…e19c
26 touches
78 conflicts
0x00000000…001f
0x1b6862…e19c
26 touches
78 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
26 touches
78 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
26 touches
78 conflicts
0x3b4dc7a8…d1a3
0xd32edf…ff58
25 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 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)
78 conflicts on slot 0x0000000000…000012
Audit this contract →
← previous block·next block →recent activity