← previous blocknext block →recent activity
Analyzing
Block #107,666,029
35 transactions · 26 stateful · 2026-09-24 17:25:06 UTC
Parallelism
89/100
Blocked
35%
Avg conflicts / tx
0.34
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,666,029 · 35 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
1w03w17w08w010w013w114w217w020w121w022w123w132w133w234w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x479ce48c…fa17
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xa07aa4b8…6037
0xd32edf…ff58
5 touches
3 conflicts
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
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)
3 conflicts on slot 0x479ce48cf3…06fa17
Audit this contract →
← previous block·next block →recent activity