← previous blocknext block →recent activity
Analyzing
Block #107,817,138
25 transactions · 19 stateful · 2026-09-25 06:06:29 UTC
Parallelism
80/100
Blocked
53%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,817,138 · 25 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
1w02w13w24w35w46w212w013w114w215w316w422w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x93e9d6dc…6aea
0x34b655…2a6f
10 touches
10 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x2b093939…908a
0x1b6862…e19c
10 touches
10 conflicts
0xaa5b0c77…21c7
0xd32edf…ff58
9 touches
10 conflicts
0x641aed07…bcb9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
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…000013
Audit this contract →
← previous block·next block →recent activity