← previous blocknext block →recent activity
Analyzing
Block #109,057,110
25 transactions · 21 stateful · 2026-09-29 14:13:57 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #109,057,110 · 25 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
1w05w06w17w212w014w115w116w320w121w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ea8fa8d…3dd4
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0xa310d2b6…5180
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0x125f12…a50b
10 touches
10 conflicts
0x00000000…0009
0x125f12…a50b
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xc8c7dc95…c784
0x34b655…2a6f
4 touches
1 conflict
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 0x6ea8fa8d6c…5d3dd4
Audit this contract →
← previous block·next block →recent activity