← previous blocknext block →recent activity
Analyzing
Block #109,170,194
22 transactions · 22 stateful · 2026-09-29 23:44:00 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #109,170,194 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w511w612w721w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x6235638c…6438
0x1b6862…e19c
16 touches
28 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001a
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002a
0x1b6862…e19c
16 touches
28 conflicts
0xac64b54c…4b07
0xd32edf…ff58
15 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 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)
28 conflicts on slot 0xd9f18d9a4a…7f141d
Audit this contract →
← previous block·next block →recent activity