← previous blocknext block →recent activity
Analyzing
Block #109,233,567
19 transactions · 16 stateful · 2026-09-30 05:02:57 UTC
Parallelism
68/100
Blocked
69%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,233,567 · 19 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
1w02w14w25w36w47w38w29w313w416w417w518w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x479ce48c…fa16
0x1b6862…e19c
10 touches
10 conflicts
0xcc76954a…4e3e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0054
0x1b6862…e19c
8 touches
6 conflicts
0x106f80f5…d417
0x1b6862…e19c
8 touches
6 conflicts
0x2dd555ab…bd72
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