← previous blocknext block →recent activity
Analyzing
Block #107,802,835
35 transactions · 31 stateful · 2026-09-25 04:54:30 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,802,835 · 35 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
2w06w17w28w310w012w013w114w215w316w117w018w120w021w133w134w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45364cf9…65d7
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x573cd095…948c
0xd32edf…ff58
9 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
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 0x45364cf92a…4a65d7
Audit this contract →
← previous block·next block →recent activity