← previous blocknext block →recent activity
Analyzing
Block #109,133,703
20 transactions · 19 stateful · 2026-09-29 20:39:58 UTC
Parallelism
55/100
Blocked
58%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #109,133,703 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 conflicts
0x2ce2d49e…d186
0x1b6862…e19c
18 touches
36 conflicts
0xff71ef0b…3b79
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0052
0x1b6862…e19c
16 touches
28 conflicts
0x4b1a00ef…9007
0x1b6862…e19c
16 touches
28 conflicts
0x615d7983…1e50
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 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)
36 conflicts on slot 0x0000000000…000013
Audit this contract →
← previous block·next block →recent activity