← previous blocknext block →recent activity
Analyzing
Block #108,942,346
23 transactions · 20 stateful · 2026-09-29 04:33:51 UTC
Parallelism
78/100
Blocked
60%
Avg conflicts / tx
1.09
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,942,346 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w09w010w111w212w317w119w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x2b093939…9088
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x5c4db9dc…dca4
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0056
0x1b6862…e19c
8 touches
6 conflicts
0x2b88485c…a737
0x1b6862…e19c
8 touches
6 conflicts
0x6c0daab7…4a63
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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)
10 conflicts on slot 0x0000000000…000015
Audit this contract →
← previous block·next block →recent activity