← previous blocknext block →recent activity
Analyzing
Block #107,785,116
29 transactions · 25 stateful · 2026-09-25 03:25:10 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,785,116 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w09w010w014w015w116w117w219w122w225w326w028w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c6f37ba…c20b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x9f3be344…6acd
0xd32edf…ff58
7 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 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)
6 conflicts on slot 0x6c6f37badb…87c20b
Audit this contract →
← previous block·next block →recent activity