← previous blocknext block →recent activity
Analyzing
Block #109,236,373
20 transactions · 18 stateful · 2026-09-30 05:17:05 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,236,373 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w110w413w516w518w019w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xada193dc…5c7c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xe6c77839…92ad
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0054
0x1b6862…e19c
8 touches
6 conflicts
0x206cc6c8…0159
0x1b6862…e19c
8 touches
6 conflicts
0x6f0f03f8…f3de
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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)
10 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity