← previous blocknext block →recent activity
Analyzing
Block #109,236,288
20 transactions · 16 stateful · 2026-09-30 05:16:40 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,236,288 · 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
2w03w14w25w36w48w09w112w114w015w119w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x9256b810…52ca
0x1b6862…e19c
12 touches
15 conflicts
0x0570520a…ce03
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0054
0x1b6862…e19c
10 touches
10 conflicts
0x9f574577…d850
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xece39774…e10f
0x1b6862…e19c
10 touches
10 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)
15 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity