← previous blocknext block →recent activity
Analyzing
Block #109,236,424
13 transactions · 12 stateful · 2026-09-30 05:17:21 UTC
Parallelism
46/100
Blocked
58%
Avg conflicts / tx
1.69
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #109,236,424 · 13 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
1w02w13w24w35w46w57w610w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe01158fd…f97f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x57460036…1621
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0040
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0054
0x1b6862…e19c
10 touches
10 conflicts
0x22e1b157…d838
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
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)
21 conflicts on slot 0xe01158fdb6…86f97f
Audit this contract →
← previous block·next block →recent activity