← previous blocknext block →recent activity
Analyzing
Block #109,176,313
26 transactions · 24 stateful · 2026-09-30 00:14:47 UTC
Parallelism
62/100
Blocked
54%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #109,176,313 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0xada193dc…5c7b
0x1b6862…e19c
20 touches
45 conflicts
0x96b39fe6…156e
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0040
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0053
0x1b6862…e19c
16 touches
28 conflicts
0x206cc6c8…0159
0x1b6862…e19c
16 touches
28 conflicts
0x6f0f03f8…f3dd
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)
45 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity