← previous blocknext block →recent activity
Analyzing
Block #109,177,129
21 transactions · 19 stateful · 2026-09-30 00:18:53 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,177,129 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w011w116w518w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x556eb67e…6e5f
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x6fd9ae7c…e97f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002a
0x1b6862…e19c
14 touches
21 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)
21 conflicts on slot 0x556eb67eb8…e96e5f
Audit this contract →
← previous block·next block →recent activity